OpenJDK / IcedTea issues

[sward]

JOSM stops responding and CPU usage jumps up after adding a way, deselecting it, and trying to select something else.

Steps to reproduce:

1. Start JOSM
2. File→New
3. Add a node
4. Add another node (create a way)
5. Return to select mode
6. Add a tag to the way, which should be selected, e.g. test=test
7. Deselect way (unselect, or click in an empty area)
8. Attempt to select one of the nodes

By bisecting working and not working revisions, I was able to trace the bug to [1353] (although I have no clue what change there could cause this behaviour).

This seems dependent on JRE, and may be a Java bug: The problem appears using a build of IcedTea Java 7:

java version "1.7.0" IcedTea Runtime Environment (build 1.7.0-b24) IcedTea Server VM (build 1.7.0-b24, mixed mode)

(I use this because it avoids a bug in previous Java versions where the  application window is blank under a tiling window manager.)

I cannot reproduce when running the following Java version (Debian package openjdk-6-jre 6b14-1.5~pre1-5) under Xephyr:

java version "1.6.0_0" OpenJDK Runtime Environment (IcedTea6 1.5pre) (6b14-1.5~pre1-5) OpenJDK Server VM (build 14.0-b10, mixed mode)

[stoecker]

Using Sun Java very likely will solve the problem. We already had lots of reports of that type.

[sward]

Replying to stoecker:

Using Sun Java very likely will solve the problem. We already had lots of reports of that type.

Just to set this one straight: OpenJDK is Sun Java. See  http://openjdk.java.net/

What you see as the Sun Java VMs actually completely fail to work in any sort of specialised window managers, resulting in various issues such as blank windows (also reported before).

Thirdly, if it is not clear, I reported this as a bug for JOSM working with OpenJDK and IcedTea, which is merely a build of OpenJDK using free software along with replacements from Classpath and stubs for components not yet available in OpenJDK itself. To my knowledge, JOSM does not use these or I do not use the functionality (last time I looked, there was sound, some crypto stuff, and a few other things that were not implemented).

Therefore, I am reopening this bug, and changing the title to reflect the above.

[sward]

I should add that I went to the effort of finding the revision where the bug appeared and I am willing to help debug this, but I will need help to do so. I completely understand if you are unable to reproduce the issue, but I am, so I am in a position to debug it given the know how.

[stoecker]

Actually from my side this is a minor issue and I wont spend time debugging it as long as there are much more important things to do, especially as the debugging time maybe multiple days work.

What you can do is to find out at which position in josm the software hangs really. If the change is really related to [1353], then probably only the properties dialog changes can be the cause. Surrounding the relevant code parts with outputs or using other debug techniques can help to find the code position. If there is some more information about that, then maybe a rough guess can be done to find the (possible) bug.

[jttt]

I've tested that with latest JOSM and openjdk 7 and it worked fine, the bug didn't show up. Can you please test it again with current JOSM and java?

java version "1.7.0_0-icedtea" OpenJDK Runtime Environment (IcedTea7 1.10-pre) (7b59-0ubuntu1~karmic~ppa3) OpenJDK Server VM (build 16.0-b03, mixed mode)

[sward]

Replying to jttt:

I've tested that with latest JOSM and openjdk 7 and it worked fine, the bug didn't show up. Can you please test it again with current JOSM and java?

Tested with JOSM 1788 but still IcedTea build 1.7.0-b24 as I haven’t been able to test with a later version yet, and I see the same issue. I’ll try a later build of OpenJDK 7 when I get chance.

In addition, this is under XFWM4 (XFCE 4 window manager) and not limited to a tiling window manager as I thought it may be earlier.

[stoecker]

Ticket #2984 has been marked as a duplicate of this ticket.

[stoecker]

Can this be closed? Other reports indicated that JOSM works fine with other Java implementations.

[sward]

Replying to stoecker:

Can this be closed? Other reports indicated that JOSM works fine with other Java implementations.

May as well. I haven’t used JOSM for a few months, let alone tried to verify it with another OpenJDK version.