Opened 14 years ago
Closed 12 years ago
#5813 closed defect (fixed)
Incorrect osm data file doesn't get opened but locked
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | Incorrect data file locked | Cc: |
Description (last modified by )
Open an incorrect data file, e.g. the attached "incorrect.osm".
JOSM reports an error.
The file doesn't get opened but is locked until JOSM is terminated.
The file can't be changed or deleted by another program.
Repository Root: http://josm.openstreetmap.de/svn Build-Date: 2011-01-04 02:31:13 Last Changed Author: stoecker Revision: 3772 Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b URL: http://josm.openstreetmap.de/svn/trunk Last Changed Date: 2011-01-03 14:04:19 +0100 (Mon, 03 Jan 2011) Last Changed Rev: 3772 Identification: JOSM/1.5 (3772 de) Memory Usage: 39 MB / 989 MB (6 MB allocated, but free) Java version: 1.6.0_23, Sun Microsystems Inc., Java HotSpot(TM) Client VM Operating system: Windows 7 Dataset consistency test: No problems found Plugin: PicLayer (24308) Plugin: livegps (21706) Plugin: measurement (22547) Plugin: surveyor (21706) Plugin: undelete (24905)
Attachments (1)
Change History (9)
by , 14 years ago
Attachment: | incorrect.osm added |
---|
comment:1 by , 14 years ago
follow-up: 3 comment:2 by , 14 years ago
I think in this case it's not worth to spend time on this. I found it just by chance and it doesn't cause trouble.
comment:3 by , 14 years ago
Forgot to enter my E-mail.
Replying to anonymous:
I think in this case it's not worth to spend time on this. I found it just by chance and it doesn't cause trouble.
comment:6 by , 12 years ago
Description: | modified (diff) |
---|---|
Owner: | changed from | to
Status: | new → needinfo |
Does it still happen ? I cannot reproduce with latest on Windows.
comment:7 by , 12 years ago
"Just for fun" tested it. JOSM just gives this message:
IllegalDataException: Zeile 5 Spalte 3: The element type "node" must be terminated by the matching end-tag "</node>".
r5576
java version "1.6.0_24"
OpenJDK Runtime Environment (IcedTea6 1.11.5) (6b24-1.11.5-1)
OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
comment:8 by , 12 years ago
Resolution: | → fixed |
---|---|
Status: | needinfo → closed |
No, it doesn't happen anymore. Now I get just the same JOSM message as malenki. The file isn't locked.
I still have Windows 7. But updated it and Java runtime regularly.
This seems to affect windows only, I could not reproduce this on my linux system.
The same problem of locked files exists with completely unrelated software running on windows as well; the respective linux version doesn't show this behaviour.