JOSM crash on overpass download

[zelonewolf@…]

What steps will reproduce the problem?

Download overpass query:

[timeout:360][out:json];
nwr["protect_class"="24"];
(._;>;);
out;

What is the expected result?

Data gets loaded

What happens instead?

"You have encountered a bug in JOSM"

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: 2020-10-03 13:42:38 +0200 (Sat, 03 Oct 2020)
Build-Date:2020-10-04 01:30:47
Revision:17084
Relative:URL: ^/trunk

Identification: JOSM/1.5 (17084 en) Windows 10 64-Bit
OS Build number: Windows 10 Home 1909 (18363)
Memory Usage: 4525 MB / 9102 MB (2940 MB allocated, but free)
Java version: 1.8.0_271-b09, Oracle Corporation, Java HotSpot(TM) 64-Bit Server VM
Look and Feel: com.sun.java.swing.plaf.windows.WindowsLookAndFeel
Screen: \Display0 1920x1080 (scaling 1.0x1.0)
Maximum Screen Size: 1920x1080
Best cursor sizes: 16x16 -> 32x32, 32x32 -> 32x32

Plugins:
+ DirectDownload (35552)
+ DirectUpload (35583)
+ FastDraw (35499)
+ ImproveOsm (202)
+ ImproveWay (29)
+ PolygonCutOut (v0.7)
+ RelationDissolve (0.2.0)
+ apache-commons (35524)
+ areaselector (368)
+ austriaaddresshelper (1597341117)
+ auto_tools (73)
+ changeset-viewer (22)
+ colorscheme (35405)
+ conflation (0.6.6)
+ contourmerge (v0.1.6)
+ dataimport (35248)
+ ejml (35313)
+ geotools (35169)
+ imagery_offset_db (35405)
+ jaxb (35092)
+ jts (35122)
+ log4j (35092)
+ merge-overlap (35583)
+ opendata (35513)
+ pbf (35605)
+ reverter (35579)
+ routes (35405)
+ turnrestrictions (35583)
+ utilsplugin2 (35608)
+ waydownloader (35405)
+ wikipedia (1.1.4)

Last errors/warnings:
- 74371.532 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 (18) of main
java.lang.NullPointerException
	at org.openstreetmap.josm.io.OsmJsonReader.readRelationMembersAndTags(OsmJsonReader.java:159)
	at org.openstreetmap.josm.io.OsmJsonReader.lambda$parseRelation$5(OsmJsonReader.java:154)
	at org.openstreetmap.josm.io.AbstractReader.parseRelation(AbstractReader.java:704)
	at org.openstreetmap.josm.io.OsmJsonReader.parseRelation(OsmJsonReader.java:154)
	at org.openstreetmap.josm.io.OsmJsonReader.parseElements(OsmJsonReader.java:88)
	at org.openstreetmap.josm.io.OsmJsonReader.parseRoot(OsmJsonReader.java:68)
	at org.openstreetmap.josm.io.OsmJsonReader.parse(OsmJsonReader.java:57)
	at org.openstreetmap.josm.io.OsmJsonReader.lambda$doParseDataSet$6(OsmJsonReader.java:180)
	at org.openstreetmap.josm.io.AbstractReader.doParseDataSet(AbstractReader.java:298)
	at org.openstreetmap.josm.io.OsmJsonReader.doParseDataSet(OsmJsonReader.java:178)
	at org.openstreetmap.josm.io.OverpassDownloadReader.parseDataSet(OverpassDownloadReader.java:383)
	at org.openstreetmap.josm.io.BoundingBoxDownloader.parseOsm(BoundingBoxDownloader.java:198)
	at org.openstreetmap.josm.io.OverpassDownloadReader.parseOsm(OverpassDownloadReader.java:389)
	at org.openstreetmap.josm.actions.downloadtasks.DownloadOsmTask$DownloadTask.parseDataSet(DownloadOsmTask.java:462)
	at org.openstreetmap.josm.actions.downloadtasks.DownloadOsmTask$DownloadTask.realRun(DownloadOsmTask.java:470)
	at org.openstreetmap.josm.gui.PleaseWaitRunnable.doRealRun(PleaseWaitRunnable.java:94)
	at org.openstreetmap.josm.gui.PleaseWaitRunnable.run(PleaseWaitRunnable.java:142)
	at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
	at java.util.concurrent.FutureTask.run(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
	at java.lang.Thread.run(Unknown Source)

[anonymous]

This bug appears to be repeatable. I routinely run JOSM with -Xmx10G.

[GerdP]

out:json looks wrong. You want xml format.

[anonymous]

Other out:json queries work with no problem whatsoever.

For example:

[timeout:360][out:json];
way["boundary"="protected_area"]["protect_class"="24"];
(._;>;);
out;

[Klumbumbus]

IIRC JOSM automatically changes out:json to out:xml (?)

edit: r13336

edit: or not, r14086

[GerdP]

Closed as duplicate of #19960.
OK, sorry, I wasn't aware of this feature (and I am not sure what it is good for). The NPE was already fixed.