#2126 closed defect (fixed)
crashed with out of heap message
Reported by: | Owned by: | framm | |
---|---|---|---|
Priority: | minor | Milestone: | |
Component: | unspecified | Version: | latest |
Keywords: | Cc: |
Description
After clicking on a georefferenced image, JOSM showed me an empty dialog box (titled 'note'). The 'close' button on the title of that dialog box is active, but does nothing. The rest of the programm beeps at me if I click anything. Console log shows:
Parser finished: Tags 495 Nodes 1431 Ways 89 Relations 12 Members 76
Data loaded!
Add/Merge data: 12% 25% 38% 50% 63% 76% 88%
java.lang.OutOfMemoryError: Java heap space
at java.awt.image.DataBufferInt.<init>(DataBufferInt.java:41)
at java.awt.image.Raster.createPackedRaster(Raster.java:458)
at java.awt.image.DirectColorModel.createCompatibleWritableRaster(DirectColorModel.java:1015)
at sun.awt.image.ImageRepresentation.createBufferedImage(ImageRepresentation.java:223)
at sun.awt.image.ImageRepresentation.setPixels(ImageRepresentation.java:482)
at apple.awt.OSXImageRepresentation.setPixels(OSXImageRepresentation.java:68)
at sun.awt.image.ImageDecoder.setPixels(ImageDecoder.java:120)
at sun.awt.image.JPEGImageDecoder.sendPixels(JPEGImageDecoder.java:97)
at sun.awt.image.JPEGImageDecoder.readImage(Native Method)
at sun.awt.image.JPEGImageDecoder.produceImage(JPEGImageDecoder.java:119)
at sun.awt.image.InputStreamImageSource.doFetch(InputStreamImageSource.java:246)
at sun.awt.image.ImageFetcher.fetchloop(ImageFetcher.java:172)
at sun.awt.image.ImageFetcher.run(ImageFetcher.java:136)
The first lines are probably unrelated to the crash.
I'm using JOSM snapshot 1334 (downloaded yesterday) on Mac OS X 10.4.11
Attachments (0)
Change History (2)
comment:1 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
comment:2 by , 16 years ago
It's ok if the application needs more memory.
But crashing and taking a lot of unsaved data with it?
I'm not that fit in java, but aren't there any possibilities to catch that exception and do an auto-save? Or at least an emergency-dump to be opened the next time the application starts?
As a workaround: Can't the application ask for more memory by default? I actually don't want to use the terminal to start the application. Yeah, I know I could write a start script. But why bother (every) user with that?
Okok, the answer probably is: this is technically no release version.
(I leave this ticket as closed, 'cause I don't expect a solution to this. But I really would like to get a comment on the problem. I hope you read comments to closed tickets. If not, I will open it agein in a few days.)
You need to give JOSM more memory. The Java commanline args or the JOSM error request should tell you how.