The PC crashed and could only with CtrlAltDel restarted.

[Hendrikklaas]

What steps will reproduce the problem?

1. Start up with a large area
2. Edit it to uptil 1100 objects.

What is the expected result?

The PC could crash

What happens instead?

Please provide any additional information below. Attach a screenshot if possible.

URL:http://josm.openstreetmap.de/svn/trunk
Repository:UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
Last:Changed Date: 2017-01-02 00:53:29 +0100 (Mon, 02 Jan 2017)
Build-Date:2017-01-02 02:33:21
Revision:11427
Relative:URL: ^/trunk

Identification: JOSM/1.5 (11427 nl) Windows 10 64-Bit
Memory Usage: 274 MB / 989 MB (46 MB allocated, but free)
Java version: 1.8.0_111-b14, Oracle Corporation, Java HotSpot(TM) Client VM
Screen: \Display0 1920x1080
Maximum Screen Size: 1920x1080
Dataset consistency test: No problems found

Plugins:
+ turnrestrictions (33088)

Last errors/warnings:
- W: Onmogelijk bestand <josm.pref>\autosave\Franklin waterholes.pid te verwijderen
- W: Onmogelijk bestand <josm.pref>\autosave\OSM Frieslandriegel Smilde eo.pid te verwijderen

Hi I stumbled over I don’t know what, I use the following configuration;
Asus P2530U Core I5 with a virtual HDD, together with JOSM 11427.
It happened lately since I installed the new version 11427 that the configuration crashed,
just to use reset to get it starting all over again.
Uploading of the dataset to the server has failed because it is wrongly or up against one rule.
The message is coded;
Response Code=412, Error header=<Precondition failed cannot create way: data is invalid.>
The latest was this new problem;
It could be caused by a large dataset of > 1100 objects, but I doubt it.
Disaster area:
​http://www.openstreetmap.org/#map=14/31.1349/-96.5509
showing several problems for instance
: double nodes, covering each other ?
: loose nodes, not connected to anything but originally part of a way.
: copied ways, on one resting on top of another one ?
Greetz

[bastiK]

The error indicates, that there was a way with 0 nodes in the upload request. JOSM should not produce a way with 0 nodes. Unfortunately it is very hard for us to figure out the cause, unless you can give step-by-step instruction on how to reproduce the error or at least provide more information on the actions performed.

The size of the dataset shouldn't matter, but it increases the chance to get "unusual" data from the server.