Openbravo Issue Tracking System - POS2
Recently, issues have surfaced during the execution of the Cypress Cash Up test on a dev server. The test tends to fail after the "Closing Till + Login" step, as it anticipates an open Till through State, while the POS renders an already opened Till, resulting in test failure.
Upon analysis, the console log error "Can't perform a React state Component.jsx:xxx update on an unmounted component. This is a no-op, but it indicates a memory leak in your application" has been identified.
Upon identifying the steps to reproduce the error, it was confirmed that this issue is specific to the development server. This could also explain the random memory leaks observed in the Jenkins code coverage job, which employs a dev server (known to be NOK) for test execution
- Open a terminal and navigate to the "openbravo" folder within your context and execute: "cd modules/org.openbravo.core2/web-jspack/org.openbravo.core2/"
- Once you're in the core2 folder, launch a dev server by executing "npm start"
- Wait for your development server to be compiled.
- From a chrome window visit " http://localhost:3000/openbravo [^] " and open chrome development Tools (Cntrl + Shift + I) and switch to "Console" tab.
- Login POS
- Set business Date and Match Initial Count
- Reload page (F5)
- Close Till (click close Till Tab and follow the steps)
- One Close Till is completed, POS will logout.
- Login again
- Observe console log message.
Screenshot from 2024-01-19 08-39-29.png (150,679) 2024-01-22 08:28https://issues.openbravo.com/file_download.php?file_id=19359&type=bug