Opened 15 years ago
Last modified 9 years ago
#5355 new defect
Infinite loop in download window on OutOfMemory — at Version 2
| Reported by: | Zverikk | Owned by: | team |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Core | Version: | |
| Keywords: | memory | Cc: |
Description (last modified by )
When OOM happens and user presses download button, a message appears concerning the OOM error. And again, and again. Seems like there's one for every tile downloaded from OSM. There is no chance to click through all these dialogs, close download window and save changes made.
User should have a chance to save his work even when there is an error.
Change History (2)
comment:1 by , 15 years ago
comment:2 by , 11 years ago
| Description: | modified (diff) |
|---|---|
| Keywords: | memory added |
Note:
See TracTickets
for help on using tickets.
part of console:
Autosave failed:
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
Exception occurred during event dispatching:
Exception occurred during event dispatching:
java.lang.OutOfMemoryError: Java heap space
Exception occurred during event dispatching:Exception occurred during event disp
atching:
Exception occurred during event dispatching:
Exception occurred during event dispatching:
Exception occurred during event dispatching:
java.lang.OutOfMemoryError: Java heap space
Exception occurred during event dispatching:
java.lang.OutOfMemoryError: Java heap space
Exception occurred during event dispatching:
java.lang.OutOfMemoryError: Java heap space
Exception occurred during event dispatching:
java.lang.OutOfMemoryError: Java heap space
Autosave failed:
java.lang.OutOfMemoryError: Java heap space
(later) on the next run, JOSM found 4 autosaves. Thank you for that feature. You should probably notify user somehow that there are autosaves, so he/she does not panic :)