Ticket #2235 (closed enhancement: duplicate)
save your edits every x minutes
| Reported by: | sergionaranja | Owned by: | team |
|---|---|---|---|
| Priority: | major | Component: | Core |
| Version: | Keywords: | ||
| Cc: |
Description
im having trouble with memory and JOSM gets stalled sometimes. So it will be a very useful enhancement to be able to set it so it saves an "utitled.osm" every x minutes automatically.
Attachments
Change History
comment:2 in reply to: ↑ 1 Changed 3 years ago by sergionaranja
Replying to stoecker:
Increase you memory supplied to Java would be a better option. The memory warning or Java docs tell you how.
I already have java -Xmx800M -jar ./josm-tested.jar (thats another issue). Saving your edits every x minutes will be good anyway, will prevent loss of data in any present or future shut-down event.
comment:3 Changed 3 years ago by xeen
Overwriting the original files doesn't seem a good idea. The user mightn't want to have it overwritten (i.e. just testing something). Instead, what about automatically saving opened data layers to temp files every x minutes (keep last 5 or so)? If JOSM doesn't shutdown properly, a dialog could be presented on the next start if the user wishes to restore one of the backed up copies.
comment:4 Changed 3 years ago by sergionaranja
yes that sounds better, and you can always toggle the feature in preferences.
comment:5 in reply to: ↑ 1 Changed 3 years ago by anonymous
Replying to stoecker:
Increase you memory supplied to Java would be a better option. The memory warning or Java docs tell you how.
Won't help if you run out of physical memory, as Java will be killed by OOM-killer or some similar mechanism. This feature would help also with crashes with causes unrelated to JOSM (blue screen of death, power outage without having UPS, etc ...), as your data are more likely to be saved...



Increase you memory supplied to Java would be a better option. The memory warning or Java docs tell you how.