EDT violations during start screen operations sometimes prevent JOSM to start

[FraMauro]

I updated josm to the last version (4667) a few days ago

The first time after the update I got no problem

Now I get an error message at the beginning (it is the first thing I see)
The message says that there is a mistake in the preferences file and that
it will save the old preference file somewhere and it will create a new
standard preference file.

After that sometimes josm starts, sometimes I get the "do you want to report a bug?"
window and no josm

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2011-12-19 02:32:42
Last Changed Author: Don-vip
Revision: 4667
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2011-12-19 00:02:30 +0100 (Mon, 19 Dec 2011)
Last Changed Rev: 4667

Identification: JOSM/1.5 (4667 it)
Memory Usage: 34 MB / 494 MB (6 MB allocated, but free)
Java version: 1.6.0, Sun Microsystems Inc., Java HotSpot(TM) 64-Bit Server VM
Operating system: Windows 2003


java.lang.ArrayIndexOutOfBoundsException: 3
	at java.awt.Container.createHierarchyEvents(Unknown Source)
	at java.awt.Container.createHierarchyEvents(Unknown Source)
	at java.awt.Container.createHierarchyEvents(Unknown Source)
	at java.awt.Container.createHierarchyEvents(Unknown Source)
	at java.awt.Container.createHierarchyEvents(Unknown Source)
	at java.awt.Container.createHierarchyEvents(Unknown Source)
	at java.awt.Component.hide(Unknown Source)
	at java.awt.Window.hide(Unknown Source)
	at java.awt.Component.show(Unknown Source)
	at java.awt.Component.setVisible(Unknown Source)
	at java.awt.Window.setVisible(Unknown Source)
	at org.openstreetmap.josm.gui.MainApplication.main(MainApplication.java:248)

[bastiK]

Please update Java or JOSM. I'm not 100% sure, but the problem should be fixed already.

[skyper]

removed duplicate lines

[simon04]

I also got this error sometimes in the last days while testing the latest versions. However, I have no idea how to reproduce it. Probably a Java bug?

[stoecker]

MainApplication.java:248 is now an empty line. The report needs to be updated.

Maybe an error in the reconstruction of the window geometry. Probably caused by broken preferences?

[simon04]

Replying to stoecker:

MainApplication.java:248 is now an empty line. The report needs to be updated.

See ​http://josm.openstreetmap.de/browser/josm/trunk/src/org/openstreetmap/josm/gui/MainApplication.java?rev=4667#L248 – splash.setVisible(false);

Maybe an error in the reconstruction of the window geometry. Probably caused by broken preferences?

I don't think so as I mostly tested with a fresh config dir.

[simon04]

Happened again today. A subsequent start succeeded.

Build-Date: 2012-03-04 19:41:43
Revision: 5032
Is-Local-Build: true

Identification: JOSM/1.5 (5032 SVN en_GB)
Memory Usage: 208 MB / 3504 MB (156 MB allocated, but free)
Java version: 1.7.0_03-icedtea, Oracle Corporation, OpenJDK 64-Bit Server VM
Operating system: Linux
Dataset consistency test: No problems found

java.lang.IndexOutOfBoundsException: Index: 3, Size: 3
	at java.util.ArrayList.rangeCheck(ArrayList.java:604)
	at java.util.ArrayList.get(ArrayList.java:382)
	at java.awt.Container.createHierarchyEvents(Container.java:1434)
	at java.awt.Container.createHierarchyEvents(Container.java:1434)
	at java.awt.Container.createHierarchyEvents(Container.java:1434)
	at java.awt.Container.createHierarchyEvents(Container.java:1434)
	at java.awt.Container.createHierarchyEvents(Container.java:1434)
	at java.awt.Container.createHierarchyEvents(Container.java:1434)
	at java.awt.Component.hide(Component.java:1689)
	at java.awt.Window.hide(Window.java:1115)
	at java.awt.Component.show(Component.java:1653)
	at java.awt.Component.setVisible(Component.java:1603)
	at java.awt.Window.setVisible(Window.java:1013)
	at org.openstreetmap.josm.gui.MainApplication.main(MainApplication.java:258)

[skyper]

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

[skyper]

From #7792: Don-vip:

I don't think this is due to Java version. Netbeans guys have a ​long history with this bug.

The issue was simply an EDT violation. And if we ​look at our code:

        ... (Splash screen operations)
        ...
        if (Main.pref.getBoolean("debug.edt-checker.enable", Version.getInstance().isLocalBuild())) {
            // Repaint manager is registered so late for a reason - there is lots of violation during startup process but they don't seem to break anything and are difficult to fix
            ...
        }

Well, it seems these violations DO break something here.

[Don-vip]

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

[Don-vip]

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

[Don-vip]

Many EDT violations have been fixed between 2013 and 2017, I think this issue is gone now.