Modify ↓
Opened 16 years ago
Closed 16 years ago
#3040 closed defect (fixed)
NPE when deleting more than one node
Reported by: | anonymous | Owned by: | team |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | Cc: |
Description
Sometimes, but not always, when deleting nodes that have been just unglued, i get the following NPE:
Manifest-Version: 1.0 Ant-Version: Apache Ant 1.7.1 Created-By: 11.3-b02 (Sun Microsystems Inc.) Main-class: JOSM Main-Version: 1823 SVN Main-Date: 2009-07-22T18:33:41.709859Z Memory Usage: 91 MB / 910 MB (44 MB allocated, but free) Java version: 1.6.0_13 Plugins: AgPifoJlakewalkerutilspluginvalidatorwmsplugin Plugin AgPifoJ Version: 16603 Plugin lakewalker Version: 16621 Plugin utilsplugin Version: 16628 Plugin validator Version: 16629 Plugin wmsplugin Version: 16599 java.lang.NullPointerException: /images/data/piste.png not found at org.openstreetmap.josm.tools.ImageProvider.get(ImageProvider.java:69) at org.openstreetmap.josm.command.DeleteCommand.description(DeleteCommand.java:102) at org.openstreetmap.josm.command.SequenceCommand.description(SequenceCommand.java:93) at org.openstreetmap.josm.gui.dialogs.CommandStackDialog.buildList(CommandStackDialog.java:73) at org.openstreetmap.josm.gui.dialogs.CommandStackDialog.commandChanged(CommandStackDialog.java:83) at org.openstreetmap.josm.data.UndoRedoHandler.fireCommandsChanged(UndoRedoHandler.java:87) at org.openstreetmap.josm.data.UndoRedoHandler.add(UndoRedoHandler.java:46) at org.openstreetmap.josm.actions.mapmode.DeleteAction.doActionPerformed(DeleteAction.java:86) at org.openstreetmap.josm.actions.mapmode.DeleteAction.actionPerformed(DeleteAction.java:70) at javax.swing.SwingUtilities.notifyAction(SwingUtilities.java:1636) at javax.swing.JComponent.processKeyBinding(JComponent.java:2849) at javax.swing.KeyboardManager.fireBinding(KeyboardManager.java:267) at javax.swing.KeyboardManager.fireKeyboardAction(KeyboardManager.java:216) at javax.swing.JComponent.processKeyBindingsForAllComponents(JComponent.java:2926) at javax.swing.JComponent.processKeyBindings(JComponent.java:2918) at javax.swing.JComponent.processKeyEvent(JComponent.java:2812) at java.awt.Component.processEvent(Component.java:5993) at java.awt.Container.processEvent(Container.java:2041) at java.awt.Component.dispatchEventImpl(Component.java:4583) at java.awt.Container.dispatchEventImpl(Container.java:2099) at java.awt.Component.dispatchEvent(Component.java:4413) at java.awt.KeyboardFocusManager.redispatchEvent(KeyboardFocusManager.java:1848) at java.awt.DefaultKeyboardFocusManager.dispatchKeyEvent(DefaultKeyboardFocusManager.java:704) at java.awt.DefaultKeyboardFocusManager.preDispatchKeyEvent(DefaultKeyboardFocusManager.java:969) at java.awt.DefaultKeyboardFocusManager.typeAheadAssertions(DefaultKeyboardFocusManager.java:841) at java.awt.DefaultKeyboardFocusManager.dispatchEvent(DefaultKeyboardFocusManager.java:668) at java.awt.Component.dispatchEventImpl(Component.java:4455) at java.awt.Container.dispatchEventImpl(Container.java:2099) at java.awt.Window.dispatchEventImpl(Window.java:2475) at java.awt.Component.dispatchEvent(Component.java:4413) at java.awt.EventQueue.dispatchEvent(EventQueue.java:599) at java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:269) at java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:184) at java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:174) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:169) at java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:161) at java.awt.EventDispatchThread.run(EventDispatchThread.java:122)
And after that, an NPE occurs when doing any modifications to the data.
Attachments (0)
Change History (2)
comment:1 by , 16 years ago
Summary: | NPE when deleting unglued nodes → NPE when deleting more than one node |
---|
comment:2 by , 16 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
This seems to be fixed in r1826
Note:
See TracTickets
for help on using tickets.
This seems to occur always when deleting more than one node that are part of the same way