Modify

Opened 7 years ago

Last modified 5 months ago

#5355 new defect

Infinite loop in download window on OutOfMemory

Reported by: Zverikk Owned by: team
Priority: normal Milestone:
Component: Core Version:
Keywords: memory Cc:

Description (last modified by Don-vip)

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.

Attachments (0)

Change History (4)

comment:1 Changed 7 years ago by Zverikk

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 :)

comment:2 Changed 3 years ago by Don-vip

Description: modified (diff)
Keywords: memory added

comment:3 Changed 5 months ago by anonymous

I note that now JOSM hangs very frequently in various operations performing some infinite loops, possibly with infinite recursions on relations somewhere in its validator.

This is an old bug that was fixed in the renderer by tracking recursions in a stack of visited relations, but visibly this is not used in every new steps added in recent versions of JOSM.

So very frequently I see these hangs just when I have finished editing, and all is OK, but then I press the upload button: JOSM suddenly takes avove 90% of CPU on all its threads and cores and the garbage collector is extremely active with a VM exploding sudently to dozens of Gigabytes, and massive use of swaps to disk (I use the 64 bit version and I have plenty of memory, this is clearly a bug).

When this happens, I can no longer close JOSM, there's no alert window about falling short of memory, the CPU starts overheating, the rest of the Windows UI becomes a bit flacky, and all I can do is CTRL+ALT+DEL to display the task manager and kill JOSM, hoping that every edits have been kept in the unsaved temporary work file (but frequently I loose the last two-three minutes of edits, and I loose any other sesssion data or changed preferences that are not saved).

comment:4 Changed 5 months ago by bastiK

anonymous, your problem is unrelated to the current ticket, please open a new bug report!

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set.
to The owner will be changed from team to the specified user.
The owner will change to Zverikk
as duplicate The resolution will be set to duplicate.The specified ticket will be cross-referenced with this ticket
The owner will be changed from team to anonymous.

Add Comment


E-mail address and name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.