#5548 closed defect (duplicate)
JOSM permanently says: it looks like JOSM crashed last time
Reported by: | frief | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | |
Keywords: | autosave | Cc: |
Description
which is wrong. It did not crash last time.
The message persists on repeated startups regardless
whether Restore, Cancel, Discard is selected.
Tried with the released version and today's latest
(3592, 3603).
The message is:
"JOSM found 1 unsaved osm data layer. It looks like JOSM crashed last time. Do you like to restore the data?"
(Typing errors belong to me. The error message could not be cut and pasted. I'll file a feature request about this)
Attachments (0)
Change History (5)
comment:1 by , 15 years ago
comment:2 by , 14 years ago
Keywords: | autosave added |
---|
comment:3 by , 14 years ago
Could you please test again with version 3677 (click "discard" - 3rd button in dialog) and report debugging output to ticket #5559?
comment:4 by , 14 years ago
Resolution: | → duplicate |
---|---|
Status: | new → closed |
I can confirm this bug. Even worse is that it is no longer possible to load a file on start-up.
I had to remove all files from ~/.josm/autosave to get JOSM to work normal again.