JOSM crashes while adding nodes

[carsten@…]

What steps will reproduce the problem?

1. Add new nodes for a new way

What is the expected result? extending the way

What happens instead? sometimes JOSM crashes.
This problem started some weeks ago (new Version?)

Please provide any additional information below. Attach a screenshot if possible.

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2014-02-27 09:27:48
Last Changed Author: simon04
Revision: 6891
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2014-02-27 08:25:03 +0100 (Thu, 27 Feb 2014)
Last Changed Rev: 6891

Identification: JOSM/1.5 (6891 de) Linux Ubuntu 13.10
Memory Usage: 256 MB / 1744 MB (63 MB allocated, but free)
Java version: 1.6.0_30, Sun Microsystems Inc., OpenJDK 64-Bit Server VM
Java package: openjdk-6-jre:amd64-6b30-1.13.1-1ubuntu2~0.13.10.1
WebStart package: icedtea-netx:amd64-1.4-3ubuntu2.1
VM arguments: [-Xbootclasspath/a:/usr/share/icedtea-web/netx.jar, -Xms8m, -Dicedtea-web.bin.name=javaws, -Dicedtea-web.bin.location=/usr/bin/javaws, -Djava.security.manager, -Djava.security.policy=/etc/icedtea-web/javaws.policy]
Dataset consistency test: No problems found

Plugin: notes (v0.9.1)
Plugin: utilsplugin2 (30277)

[skyper]

Could you please add the summary of the crash ? - Thanks

This sounds like the problem with openjdk6 on debian-based distros (#8921). Please use openjdk7.

[Don-vip]

Reporting a crash without any error message do not help us, you know :(

[carsten@…]

Sorry, but there was no error message. You just add a node to an existing line and sometimes JOSM crashes. There is nothing left, it just disappears.
Now I was able to start JOSM with openjdk7. No more problems.
Thank for your help

[skyper]

Replying to carsten@…:

Sorry, but there was no error message. You just add a node to an existing line and sometimes JOSM crashes. There is nothing left, it just disappears.

No window offering to report the crash ? Then this is a bug on its own.

You could try to start josm from a terminal and hopefully find the problem within the console output.

Now I was able to start JOSM with openjdk7. No more problems.
Thank for your help

You are welcome.

[carsten@…]

No, absolutely nothing. It just disappears.
I found some log files in my home directory with names "hs_err_pdxxxx.log".
It starts with:

-------------------- snipp -------------------------
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007fae6d5370f8, pid=3350, tid=140386926139136
#
# JRE version: 6.0_30-b30
# Java VM: OpenJDK 64-Bit Server VM (23.25-b01 mixed mode linux-amd64 compressed oops)
# Problematic frame:
# J  sun.awt.X11.XGlobalCursorManager.updateGrabbedCursor(Ljava/awt/Cursor;)V
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
#   https://bugs.launchpad.net/ubuntu/+source/openjdk-6/
#

---------------  T H R E A D  ---------------

Current thread (0x0000000000b8f800):  JavaThread "AWT-EventQueue-4" [_thread_in_Java, id=3378, stack(0x00007fae60cd1000,0x00007fae60dd2000)]

siginfo:si_signo=SIGSEGV: si_errno=0, si_code=1 (SEGV_MAPERR), si_addr=0x0000000000000008
--------------------- snipp -----------------

To force JOSM to use openjdk7, I deleted openjdk6 and changed the start command for JOSM.
So it is not trivial to reproduce the error.
But if it will help you, let me know.

[skyper]

Replying to carsten@…:

No, absolutely nothing. It just disappears.
I found some log files in my home directory with names "hs_err_pdxxxx.log".

Mmh, did you check the creation time of the files ? It could be unrelated and/or old.

To force JOSM to use openjdk7, I deleted openjdk6 and changed the start command for JOSM.

You can use both at the same time. To set the default you need to run:

sudo update-alternatives -c java

So it is not trivial to reproduce the error.

You can download the .jar file and start it from the terminal like this:

/usr/lib/jvm/java-6-openjdk-amd64/bin/java -jar PATH_TO_FILE/JAR_FILE

But if it will help you, let me know.

Cannot tell for sure, but as it is planned to switch to java 7 this summer, I guess this is quite low priority and if it is a java bug we can not do anything anyway. Probably not worth the time to investigate.

[anonymous]

Hi, the date of the file was a date with a failure and JOSM was mentioned within the file.
Because JOSM will change to java 7, I think too, it is not worth to investigate further on.
Thank you for your help.
Can you close the ticket?

[Don-vip]

Replying to carsten@…:

# If you would like to submit a bug report, please include
# instructions how to reproduce the bug and visit:
# ​https://bugs.launchpad.net/ubuntu/+source/openjdk-6/

As stated in the error message, this is not JOSM's fault here.