XML document structures must start and end within the same entity.

[rogerstb@…]

What steps will reproduce the problem?

1. Open JOSM
2. Load file

What is the expected result?
Restores the lost data after JOSM crashed.

What happens instead?
Won't load the autosave file.

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

Repository Root: http://josm.openstreetmap.de/svn
Build-Date: 2014-08-31 21:55:55
Last Changed Author: Don-vip
Revision: 7480
Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b
URL: http://josm.openstreetmap.de/svn/trunk
Last Changed Date: 2014-08-31 23:51:24 +0200 (Sun, 31 Aug 2014)
Last Changed Rev: 7480

Identification: JOSM/1.5 (7480 en_GB) Windows 7 64-Bit
Memory Usage: 71 MB / 247 MB (33 MB allocated, but free)
Java version: 1.7.0_67, Oracle Corporation, Java HotSpot(TM) Client VM
VM arguments: [-Djava.security.policy=file:C:\Program Files (x86)\Java\jre7\lib\security\javaws.policy, -DtrustProxy=true, -Djnlpx.home=<java.home>\bin, -Djnlpx.origFilenameArg=C:\Program Files (x86)\JOSM\josm.jnlp, -Djnlpx.remove=true, -Djava.util.Arrays.useLegacyMergeSort=true, -Djnlpx.splashport=60619, -Djnlpx.jvm=<java.home>\bin\javaw.exe, -Djnlpx.vmargs=LURqYXZhLnV0aWwuQXJyYXlzLnVzZUxlZ2FjeU1lcmdlU29ydD10cnVlAA==]

Plugins:
- AddrInterpolation (30416)
- DirectDownload (30416)
- FastDraw (30416)
- HouseNumberTaggingTool (30416)
- OpeningHoursEditor (30609)
- PicLayer (30436)
- alignways (30416)
- buildings_tools (30485)
- continuosDownload (28565)
- graphview (30416)
- jts (30416)
- log4j (30416)
- merge-overlap (30416)
- namemanager (30416)
- notes (v0.9.4)
- reltoolbox (30587)
- routes (30416)
- tageditor (30488)
- terracer (30614)
- todo (29154)
- turnrestrictions (30454)
- utilsplugin2 (30460)
- videomapping (30416)

Last errors/warnings:
- E: Failed to locate image 'ES_s22.png'
- W: Could not get presets icon ES_s22.png
- E: org.openstreetmap.josm.io.IllegalDataException: Line 765 column 1: XML document structures must start and end within the same entity.. Cause: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[765,1]
- E: org.openstreetmap.josm.io.IllegalDataException: Line 765 column 1: XML document structures must start and end within the same entity.. Cause: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[765,1]
- E: org.openstreetmap.josm.io.IllegalDataException: Line 765 column 1: XML document structures must start and end within the same entity.. Cause: javax.xml.stream.XMLStreamException: ParseError at [row,col]:[765,1]

[rogerstb@…]

osm data layer producing XML incomplete fault

[Don-vip]

JOSM didn't crash but informed you that your file is invalid, which is the case.

[rogerstb@…]

Replying to Don-vip:

JOSM didn't crash but informed you that your file is invalid, which is the case.

Hi thanks for the reply. In fact you're quite right it didn't technically crash, however an error message box appeared this morning (although it didn't display any text within it) and the application froze. After waiting for some time, hoping to be able to acknowledge the error, or for it to resolve itself, I had to force the app to close from the windows Task Manager. I returned to the re-open the application this evening aware that I would need to restore the autosave file, and then encountered this problem with the recovery file.

In the autosave folder there is also a .osm~ file (0kb) and a .pid file (1kB), but I'm worried the autosave has failed and I won't be can't recover the lost work

[Don-vip]

Replying to rogerstb@…:

Hi thanks for the reply. In fact you're quite right it didn't technically crash, however an error message box appeared this morning (although it didn't display any text within it) and the application froze.

Without relevant technical info on this error there's nothing we can do. The best I can assume is that you didn't allocate enough memory to JOSM, see InstallNotes#MicrosoftWindows and Download#VMselectiononWindowsx64 about how allocating more memory.

In the autosave folder there is also a .osm~ file (0kb) and a .pid file (1kB), but I'm worried the autosave has failed and I won't be can't recover the lost work

Maybe JOSM turned out of memory during the autosave (just a wild guess as you have a very low value):

Memory Usage: 71 MB / 247 MB (33 MB allocated, but free)

You're right, the complete data can't be recovered. The best you can do is manually edit your file, add the missing XML tag and check if you can recover some data, but be extremely careful if you go this way: the file will be corrupted anyway, a lot of data will be missing, and unexpected behaviour may occur.

I'm sorry to close again this ticket but there's nothing more we can do with the information we have.