Modify ↓
#16045 closed defect (fixed)
NPE in Relation > Tags and Members
| Reported by: | Owned by: | team | |
|---|---|---|---|
| Priority: | normal | Milestone: | 18.03 |
| Component: | Core | Version: | |
| Keywords: | template_report relation preset regression | Cc: |
Description
What steps will reproduce the problem?
In JOSM I went to edit relation 1966414 (https://www.openstreetmap.org/relation/1966414)
Above the tags it shows "Relations/Routes/Railway Route ...".
I clicked on this (trying to figure out how to add this to a new relation I'm creating) and the error occurred
What is the expected result?
What happens instead?
Please provide any additional information below. Attach a screenshot if possible.
URL:https://josm.openstreetmap.de/svn/trunk Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b Last:Changed Date: 2018-03-01 10:08:48 +0100 (Thu, 01 Mar 2018) Build-Date:2018-03-01 09:12:13 Revision:13478 Redirecting:to URL 'https://josm.openstreetmap.de/svn/trunk': Relative:URL: ^/trunk Identification: JOSM/1.5 (13478 en_GB) Windows 10 64-Bit OS Build number: Windows 10 Pro 1709 (16299) Memory Usage: 462 MB / 910 MB (189 MB allocated, but free) Java version: 1.8.0_131-b11, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM Screen: \Display0 1920x1200 Maximum Screen Size: 1920x1200 Dataset consistency test: No problems found Plugins: + imagery_offset_db (33774) + pbf (33568) + turnrestrictions (33780) Last errors/warnings: - E: java.lang.NumberFormatException: For input string: ". : File %UserProfile%\Documents\WindowsPowerShell\Microsoft.PowerShell_profile.ps1 cannot be loaded because running - W: No configuration settings found. Using hardcoded default values for all pools. - E: org.openstreetmap.josm.io.IllegalDataException: Missing attribute 'version' on OSM primitive with ID 9709539. (at line 6, column 57). 353 bytes have been read. Cause: org.openstreetmap.josm.io.XmlStreamParsingException: Missing attribute 'version' on OSM primitive with ID 9709539. (at line 6, column 57). 353 bytes have been read - E: Error - <html>Could not read file 'GB.osm'.<br>Error is:<br>Missing attribute 'version' on OSM primitive with ID 9709539. (at line 6, column 57). 353 bytes have been read</html> - E: org.openstreetmap.josm.io.IllegalDataException: Missing attribute 'version' on OSM primitive with ID 9709539. (at line 6, column 57). 353 bytes have been read. Cause: org.openstreetmap.josm.io.XmlStreamParsingException: Missing attribute 'version' on OSM primitive with ID 9709539. (at line 6, column 57). 353 bytes have been read - E: Error - <html>Could not read file 'GB.osm'.<br>Error is:<br>Missing attribute 'version' on OSM primitive with ID 9709539. (at line 6, column 57). 353 bytes have been read</html> - E: org.openstreetmap.josm.io.IllegalDataException: Missing attribute 'version' on OSM primitive with ID 2388649422. (at line 79,676, column 60). 6,164,879 bytes have been read. Cause: org.openstreetmap.josm.io.XmlStreamParsingException: Missing attribute 'version' on OSM primitive with ID 2388649422. (at line 79,676, column 60). 6,164,879 bytes have been read - E: Error - <html>Could not read file 'GB.osm'.<br>Error is:<br>Missing attribute 'version' on OSM primitive with ID 2388649422. (at line 79,676, column 60). 6,164,879 bytes have been read</html> - W: Unsaved changes - <html>The relation has been changed.<br><br>Do you want to save your changes?</html> - E: Handled by bug report queue: java.lang.NullPointerException === REPORTED CRASH DATA === BugReportExceptionHandler#handleException: No data collected. Warning issued by: BugReportExceptionHandler#handleException === STACK TRACE === Thread: AWT-EventQueue-0 (19) of main java.lang.NullPointerException at org.openstreetmap.josm.gui.tagging.presets.TaggingPreset.showDialog(TaggingPreset.java:495) at org.openstreetmap.josm.gui.dialogs.properties.PresetListPanel$LabelMouseAdapter.mouseClicked(PresetListPanel.java:41) at java.awt.AWTEventMulticaster.mouseClicked(Unknown Source) at java.awt.Component.processMouseEvent(Unknown Source) at javax.swing.JComponent.processMouseEvent(Unknown Source) at java.awt.Component.processEvent(Unknown Source) at java.awt.Container.processEvent(Unknown Source) at java.awt.Component.dispatchEventImpl(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source) at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source) at java.awt.Container.dispatchEventImpl(Unknown Source) at java.awt.Window.dispatchEventImpl(Unknown Source) at java.awt.Component.dispatchEvent(Unknown Source) at java.awt.EventQueue.dispatchEventImpl(Unknown Source) at java.awt.EventQueue.access$500(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.awt.EventQueue$3.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue$4.run(Unknown Source) at java.awt.EventQueue$4.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(Unknown Source) at java.awt.EventQueue.dispatchEvent(Unknown Source) at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source) at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.pumpEvents(Unknown Source) at java.awt.EventDispatchThread.run(Unknown Source)
Attachments (1)
Change History (6)
by , 6 years ago
comment:1 by , 6 years ago
| Milestone: | → 18.03 |
|---|
comment:2 by , 6 years ago
| Keywords: | relation preset regression added |
|---|
comment:4 by , 6 years ago
| Summary: | Unexpected exception in Relation > Tags and Members → NPE in Relation > Tags and Members |
|---|
Note:
See TracTickets
for help on using tickets.
Erroring screen