Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
ID | ||||||||||||
0051222 | ||||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
defect | [Modules] Advanced Warehouse Operations | critical | have not tried | 2022-12-21 13:48 | 2023-05-29 13:14 | |||||||
Reporter | cberner | View Status | public | |||||||||
Assigned To | Triage Omni WMS | |||||||||||
Priority | normal | Resolution | open | Fixed in Version | ||||||||
Status | new | Fix in branch | Fixed in SCM revision | |||||||||
Projection | none | ETA | none | Target Version | ||||||||
OS | Any | Database | Any | Java version | ||||||||
OS Version | Database version | Ant version | ||||||||||
Product Version | SCM revision | |||||||||||
Regression date | ||||||||||||
Regression introduced by commit | ||||||||||||
Regression level | ||||||||||||
Review Assigned To | ||||||||||||
Regression introduced in release | ||||||||||||
Summary | 0051222: scanEvents and selectedLine data is currently persisted in localStorage and never removed | |||||||||||
Description | When we scan an item from Inventory Count or Distribution Order(as examples), a scan event is saved in localStorage under the key "scanEvents". This events are saved per document and are never removed from the local storage, not even when the document has been completed/processed. This will result in problems if the terminal is used long enough, as the localStorage usage will keep growing until it reaches the limit(5MB in chrome). And when that limit is reached, the state persistence will start failing, as it is also saved in local storage. Which might result in application not working properly. Also, when a document is opened and a line is selected, an entry is added to localstorage "selectedLine" property, which only increases and is never removed. | |||||||||||
Steps To Reproduce | ## Prior, assign some UPC/EAN to a product so it is scaneable 1. Login AWO 2. Go to Count(Inventory Count) and start the counting process 3. Try to scan some items After scan, check in devtools: Application -> LocalStorage -> scanEvents, you should be able to see some events there. Try to complete the inventory count, and see that the events are still there. Also check the selectedLine localstorage property, it gets bigger the more documents you open with a line selected: OB.UTIL.localStorage.getItem('selectedLine'); | |||||||||||
Tags | No tags attached. | |||||||||||
Attached Files | ||||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | |
Notes | |
(0150411) AugustoMauch (administrator) 2023-05-29 13:14 edited on: 2023-05-29 13:17 |
Upgrade to critical because the memory leak can render the application unusable, specially if the same terminal is used both for AWO and POS |
Issue History | |||
Date Modified | Username | Field | Change |
2022-12-21 13:48 | cberner | New Issue | |
2022-12-21 13:48 | cberner | Assigned To | => Triage Omni WMS |
2022-12-22 09:24 | cberner | Steps to Reproduce Updated | View Revisions |
2023-01-13 10:59 | cberner | Summary | scanEvents data is currently persisted in localStorage and never removed => scanEvents and selectedLine data is currently persisted in localStorage and never removed |
2023-01-13 10:59 | cberner | Description Updated | View Revisions |
2023-01-13 10:59 | cberner | Steps to Reproduce Updated | View Revisions |
2023-05-29 13:14 | AugustoMauch | Note Added: 0150411 | |
2023-05-29 13:14 | AugustoMauch | Severity | major => critical |
2023-05-29 13:17 | AugustoMauch | Note Edited: 0150411 | View Revisions |
Copyright © 2000 - 2009 MantisBT Group |