#5761 closed defect (worksforme)
Out of memory
Reported by: | ch70 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | memory | Cc: |
Description (last modified by )
After working for hours (fortunately with some uploads in between) I got the following error message while I was browsing the presets:
"JOSM is out of memory. Strange things may happen. Please restart JOSM with the -Xmx###M option, where ### is the number of MB assigned to JOSM (e.g. 256). Currently, 109 MB are available to JOSM."
Confirming the message box, JOSM was still responding although very slowly. I tried to restart or quit JOSM several times but unfortunately none of these actions where performed. Instead the same error message box as previously popped up again thus I killed the application.
I used version 3706 on a Linux box (Ubuntu 10.04).
Attachments (0)
Change History (8)
comment:1 by , 14 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:2 by , 14 years ago
I haven't used any options (especially I haven't assigned any memory) but left the default options.
This is the command line (executed by a script):
/usr/lib/jvm/java-6-sun/bin/java -jar /usr/share/josm/josm.jar
My impression is rather that there is a memory leak (although it would be hard - if not impossible - to find it in this situation).
comment:3 by , 14 years ago
Sure, there can be memory leaks. Some have been identified and fixed in the past. But it is not unusual that JOSM needs more than 100M memory for certain tasks (imagery, photos, large data sets), so starting it without options is risky and it's your own responsibility when it crashes. :)
comment:4 by , 14 years ago
There should be at least enough memory to save and close JOSM, whenever the message is shown.
I ran into this problem several times trying to upload and validator did not get enough memory. Fortunatly I was able to save, close JOSM and upload with the next session
follow-up: 6 comment:5 by , 12 years ago
I've got the same problem. JOSM goes out of memory. With both OpenJDK and Sun Java this is happending.
But in fact I am assigning not just some MB - I am assigning some GB. But there is obviously a memory leak.
It might be related to aerial pictures but it might be also a coincidence.
It does not matter which JOSM version I am using. This happens since several months.
comment:6 by , 12 years ago
Description: | modified (diff) |
---|
Replying to anonymous:
I've got the same problem. JOSM goes out of memory. With both OpenJDK and Sun Java this is happending.
But in fact I am assigning not just some MB - I am assigning some GB. But there is obviously a memory leak.
It might be related to aerial pictures but it might be also a coincidence.
It does not matter which JOSM version I am using. This happens since several months.
Please, open a new ticket and add your system info (see status report). If possible attach an example .osm file. What kind of aerial pictures are you using ? Maybe you could try older versions and find the code change which introduced the leak.
Thanks
This is not an error, if you assign to little memory, the problem is expected. To avoid this, do as the text says: