#5559 closed defect (fixed)
josm still does not use or even delete saved osm-states
Reported by: | wambacher | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | autosave | Cc: |
Description
hi, still the old problem - for me -
i can only delete the autosave-directory to get rid of that stuff.
some older release "fixed" that bug, but i don't see any changes.
i'm using version 3609 but i've seen NO version dealing with that problem.
regards
walter
Attachments (5)
Change History (17)
by , 14 years ago
by , 14 years ago
comment:1 by , 14 years ago
follow-up: 3 comment:2 by , 14 years ago
Next time this happen, can you please run it in strace? The command would be:
strace -f -o strace.log java -jar josm-latest.jar
Start josm, click on Discard button, close josm and attach strace.log to this ticket.
comment:3 by , 14 years ago
Replying to jttt:
Next time this happen, can you please run it in strace? The command would be:
strace -f -o strace.log java -jar josm-latest.jar
Start josm, click on Discard button, close josm and attach strace.log to this ticket.
done.
regards
walter
comment:4 by , 14 years ago
Added debug output in [3675], could you please run again, click on "discard" (3rd button, just to avoid misunderstanding) and report the console output?
(I looked at the strace. There should be 2 attempts to read/list the autosave folder: one on start and one after you clicked the discard button. But only the first is present, which leads me to believe that for some reason, some code isn't executed at all.)
comment:7 by , 14 years ago
comment:11 by , 14 years ago
Resolution: | → fixed |
---|---|
Status: | new → closed |
found that #5548 is the same problem but less infos.