#5507 closed defect (othersoftware)
progress bar kills josm / segmentation violation
| Reported by: | Cobra | Owned by: | team |
|---|---|---|---|
| Priority: | blocker | Milestone: | |
| Component: | Core | Version: | latest |
| Keywords: | Cc: |
Description
JOSM crashes when displaying a progress bar, e.g. while opening many files or while downloading the list of plugins in the preferences dialog.
I'm using ubuntu 10.10 Beta/64 Bit now, I didn't notice this behaviour with my old system (ubuntu 10.04/32 Bit).
This could be a bug in the JVM code, but maybe we could either get some more details or find a workaround.
This may be related to #5506.
JOSM version information:
Repository Root: http://josm.openstreetmap.de/svn Build-Date: 2010-09-25 01:31:20 Last Changed Author: bastiK Revision: 3561 Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b URL: http://josm.openstreetmap.de/svn/trunk Last Changed Date: 2010-09-24 18:48:14 +0200 (Fri, 24 Sep 2010) Last Changed Rev: 3561
Java's message:
# # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00007f67dc346ff9, pid=29619, tid=140083940497168 # # JRE version: 6.0_20-b02 # Java VM: Java HotSpot(TM) 64-Bit Server VM (16.3-b01 mixed mode linux-amd64 ) # Problematic frame: # C [libGL.so.1+0x4bff9] # # An error report file with more information is saved as: # hs_err_pid29619.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # The crash happened outside the Java Virtual Machine in native code. # See problematic frame for where to report the bug. #
Said file is attached.
Attachments (2)
Change History (5)
by , 15 years ago
| Attachment: | hs_err_pid29619.log added |
|---|
comment:1 by , 15 years ago
by , 15 years ago
| Attachment: | hs_err_pid2240.log added |
|---|
comment:2 by , 15 years ago
| Resolution: | → othersoftware |
|---|---|
| Status: | new → closed |
Your log suggests, that the error is in libGL.so which is used for OpenGL/GLX. This is a little strange if you haven't set -Dsun.java2d.opengl=true.
Might help to change the driver for your graphics card, but this is just a wild guess. Certainly there is not much we can do about it in JOSM, so I close for now. If you found a solution, please report.
comment:3 by , 15 years ago
Heh. Seems like it's really the graphics driver... just switched to ati graphics instead of intel and everything looks fine so far.
So it must really be a bug in this driver. Sorry for the noise.



The same happens with OpenJDK:
This file is attached as well.