JOSM throws multiple bug windows when merging layers

[longiaru@…]

This is my second occurrence of JOSM crashing when merging CanVec data down onto an OSM layer. See #6444, closed because the error was irreproducible. After doing merge, bug window appears and cannot be closed without another replacing it. Only way to exit JOSM is to kill it. Upon restart, data are successfully restored into single merged layer.

Only other software running was VirtualBox running Windows XP in another workspace, consuming 1.5 of 3.5 GB memory. Machine is a P4 with GeForce 6200 running Ubuntu 11.04, 2.6.38-8 kernel.

Repository Root: ​http://josm.openstreetmap.de/svn
Build-Date: 2011-07-04 01:31:38
Last Changed Author: stoecker
Revision: 4201
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: ​http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2011-07-04 00:07:05 +0200 (Mon, 04 Jul 2011)
Last Changed Rev: 4201

Identification: JOSM/1.5 (4201 en)
Memory Usage: 183 MB / 494 MB (77 MB allocated, but free)
Java version: 1.6.0_22, Sun Microsystems Inc., OpenJDK Client VM
Operating system: Linux
Dataset consistency test: No problems found

Plugin: buildings_tools (26174)
Plugin: turnrestrictions (26174)

java.lang.IndexOutOfBoundsException: Index: 2, Size: 2

at java.util.ArrayList.rangeCheck(ArrayList.java:571)
at java.util.ArrayList.get(ArrayList.java:349)
at java.util.Collections$UnmodifiableList.get(Collections.java:1170)
at org.openstreetmap.josm.gui.dialogs.LayerListDialog$LayerListModel.setValueAt(LayerListDialog.java:1305)
at javax.swing.JTable.setValueAt(JTable.java:2743)
at javax.swing.JTable.editingStopped(JTable.java:4728)
at javax.swing.AbstractCellEditor.fireEditingStopped(AbstractCellEditor.java:142)
at javax.swing.DefaultCellEditor$EditorDelegate.stopCellEditing(DefaultCellEditor.java:366)
at javax.swing.DefaultCellEditor.stopCellEditing(DefaultCellEditor.java:231)
at javax.swing.JTable$CellEditorRemover.propertyChange(JTable.java:5970)
at java.beans.PropertyChangeSupport.fire(PropertyChangeSupport.java:298)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:292)
at java.beans.PropertyChangeSupport.firePropertyChange(PropertyChangeSupport.java:229)
at java.awt.KeyboardFocusManager.firePropertyChange(KeyboardFocusManager.java:1420)
at java.awt.KeyboardFocusManager.setGlobalPermanentFocusOwner(KeyboardFocusManager.java:712)
at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:539)
at java.awt.Component.dispatchEventImpl(Component.java:4499)
at java.awt.Container.dispatchEventImpl(Container.java:2103)
at java.awt.Component.dispatchEvent(Component.java:4455)
at sun.awt.X11.XWindow$1.run(XWindow.java:401)
at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:226)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:647)
at java.awt.EventQueue.access$000(EventQueue.java:96)
at java.awt.EventQueue$1.run(EventQueue.java:608)
at java.awt.EventQueue$1.run(EventQueue.java:606)
at java.security.AccessController.doPrivileged(Native Method)
at java.security.AccessControlContext$1.doIntersectionPrivilege(AccessControlContext.java:105)
at java.awt.EventQueue.dispatchEvent(EventQueue.java:617)
at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:275)
at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:200)
at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:190)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:185)
at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:177)
at java.awt.EventDispatchThread.run(EventDispatchThread.java:138)

[stoecker]

Can you reproduce it now? Do you have files which cause this effect to be reproducible?

[longiaru@…]

No, it is not that simple. My usual procedure is to open the CanVec data in one layer and import existing OSM data into another. Then, as in this case, I selectively merge data where appropriate from the CanVec layer to the OSM, deleting from the CanVec layer those data that have been merged. In the case of both #6444 and #6555, the errors were thrown when I finally attempted to "merge layer" any remaining data from the CanVec layer to the OSM layer.

The error is not reproducible as I do not normally save the edited CanVec and OSM layers before merging them as a layer into OSM. Also, the procedure of editing the CanVec data and then merging what data is left is something that in a vast majority of cases works without error -- I have encountered this error only twice in over 300 file imports.

Unfortunately, by the time the error occurs, JOSM is not in a state where I can save the layers in separate files for later testing. The closing of one bug notification window only opens another and all functionality in the program is lost.

The properly merged OSM data are restored upon restarting JOSM and the data are making it ultimately to the OSM server intact. So I guess at this point, the error is a nuisance only.

Thanks.

[stoecker]

If I read the bug correctly the dialog to display the layers has a bug. The question is what condition triggers it.

[Cobra]

Could you save the layers before starting the merge process? Just in case, so you could try to reproduce this when it happens again.

[anonymous]

OK... will do.