Opened 13 years ago
Closed 13 years ago
#6252 closed defect (fixed)
Phantom "unsaved" layers in 4021, 4032
Reported by: | T99 | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | tested |
Keywords: | autosave, save, unsaved, 4021, 4032 | Cc: |
Description
Whenever I start JOSM 4021, it reports finding unsaved osm data layers, sometimes hundreds of them. The error message says:
"Unsaved osm data: JOSM found %d unsaved osm data layers. It looks like JOSM crached last time. Do you like to restore the data?"
However, but I don't recall this version ever crashing on me. (Once I exited the program and explicitly told it to discard rather than save the data.)
If I discard the "unsaved data" and exit JOSM without downloading or opening any data, then the next startup works without this error message. But after any subsequent edits, the next startup shows the message again.
It looks like the autosave feature is leaving some files behind. It should remove all "unsaved" data when it's saved or uploaded successfully.
Also, please change the question "Do you like to restore the data?" to "Would you like to restore the data?".
There is an old, closed bug 5656 which may have been similar.
Attachments (1)
Change History (10)
by , 13 years ago
Attachment: | Untitled.png added |
---|
comment:2 by , 13 years ago
Keywords: | 4032 added |
---|---|
Summary: | Phantom "unsaved" layers in 4021 → Phantom "unsaved" layers in 4021, 4032 |
comment:5 by , 13 years ago
How do you close JOSM?
156 unsaved layers is a lot, do these numbers increase from one session to the next? Do you click 'discard' or 'ok'?
JOSM puts the data layers in 'autosave' folder in your preferences, please add a list of files in this folder. See Help/ResetPreferences how to locate the preferences.
comment:6 by , 13 years ago
JOSM seems to create emtpy (0 bytes) files in this folder every few minutes, with file names like:
Data Layer 1_20110804_1702.osm~
Data Layer 1_20110804_1711.osm~
Data Layer 1_20110804_1718.osm~
The empty files remain when I exit JOSM. (Only the big .osm file is removed.)
I just updated to 4279 and the bug is still present. (But thanks for correcting the message!)
When I start, I typically use the discard option and the files are removed at this time.
comment:7 by , 13 years ago
It seems, that for each file "Data Layer 1_20110804_1702.osm", that is created by the JOSM autosave feature, for some reason it creates an empty file with trailing tilde. After 5 min, JOSM removes the file without the tilde and starts all over. This explains the large number of (empty) files.
Maybe there is another software, that interferes with JOSM and causes these "secondary" backups? What's your OS?
comment:8 by , 13 years ago
This is still the same Vista 64-bit as originally reported. The current Java is 1.6.0_29. JOSM 4667 still has the bug.
error message image