#2514 closed defect (wontfix)
JOSM crash
| Reported by: | FabC | Owned by: | team |
|---|---|---|---|
| Priority: | major | Milestone: | |
| Component: | unspecified | Version: | |
| Keywords: | Cc: |
Description
After a certain number of edit operations JOSM suddenly crash. This is occuring almost randomicaly, during editing and/or when uploading data changes. A hs_err_pidxxx.log is left in the gpx data folder (copy of one of them is attached).
Attachments (1)
Change History (7)
by , 16 years ago
| Attachment: | hs_err_pid816.log added |
|---|
comment:1 by , 16 years ago
The crash has been experienced through several version of JOSM (latest used was 1566) and of JAVA.
comment:2 by , 16 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
The logfile does not contain really helpful information. But when none of the JOSM crash error messages appear I fear this is a JAVA installation issue.
comment:3 by , 16 years ago
When you get any additional information which may show an JOSM related issue, then reopen that report or add a new one. The minimum is that a stacktrace or other text contain a position inside the josm code (there must be "josm" somewher in the source code file path).
comment:5 by , 16 years ago
Copying from mailinglist:
From: Fabrizio Carrai
It looks like I found the solution!!!
It seems to "happen with machines with low video ram". I've an NVidia
Geoforce 6150 (shared memory 512MB): no idea if it falls in such category,
but now it works!
As in 1 the solution is to start JOSM including the Java option
"sun.java2d.d3d=false":
C:\WINDOWS\system32\javaw.exe -Dsun.java2d.d3d=false -Xmx800M -jar
C:\Programmi\Josm\josm-latest.jar
I'm now working since several hours with JOSM doing several changes and
uploads: no crashes till now! Before it was happening after very short
editing sessions.
Continuing testing!
Log file created after JOSM crash