JOSM sometimes not saving properly

[Roadsguy]

Not sure if this is where I should be posting this, but I couldn't find a better place.

I sometimes work on a custom .osm file made up of fictional fixes for various road situations (e.g. freeways where there aren't, rationalizing interchange setups, etc.) for fun, but sometimes it somehow doesn't save properly. I frequently do CTRL+S out of habit, but sometimes closing it and coming back to it later shows that a lot of what I had previously done did not save. This seems to be unpredictable. I'm not sure if leaving it open for a while affects it.

While what I'm doing may not be important to OSM at all, progress on anything not saving when it should is definitely a major issue.

EDIT 5/9/14: It happened yet again. Looking at my OSM file, the "last modified" time was before I had made the changes that didn't save. This means JOSM isn't even touching the file! Perhaps a Windows setting is interfering here?

[skyper]

We need more information. Could you please post your system information. See Help -> Show Status Report -> Report Bug (button on the bottom). Some Coordinates and maybe a corrupt file are useful, too.

I am not sure, if I had a similar problem, but I suspect that the keyboard shortcuts sometimes do not work properly. Could you try it with the buttons from layer list or main menu "File". Thanks

EDT: That was me (skyper)

[anonymous]

I'm running Windows 7 with Java 7 Update 51.

I don't think it's the keyboard shortcut not working, because when I go to close it, it doesn't automatically check off "Save" as an action to do before exiting like it does with "Upload." The shortcut also works most of the time anyway.

[Don-vip]

Next time you have this problem, can you please attach:

• a screenshot of the save/quit dialog
• your related .osm file
• the first three blocks of Help->Show Status Report

Thanks

[Roadsguy]

I'm not sure what you meant by "first three blocks," or what a screenshot of the save dialog would do since it wouldn't be as it was during the glitch, but I attached the first three paragraphs (down to installed plugins), and a screenshot of how I set it when I close JOSM, with a background of the most recent place where it happened. The red lines shown are where I had new ways drawn (not going far out of the shown map area) that are now gone.

My OSM file is too big to attach.

[skyper]

Replying to Roadsguy:

My OSM file is too big to attach.

Did you try to zip it ? If it is still to big, maybe, it is possible to make it available somewhere else.

[anonymous]

It just happened again. It's as if it thinks it saves, but it had never touched the file. i.e. in the closing dialog, it doesn't automatically check off "Save," yet when I look at the file, I can see that it hadn't been modified recently at all.

Here's the file as of now: ​http://www.mediafire.com/download/2x3b0y8ero4uliv/FSM.zip

[Roadsguy]

(EDIT: Above comment was me.)

Does the file size have any effect on it? Might the temporary ".osm~" file have anything to do with it?

[Roadsguy]

Update: What seems to be happening is JOSM thinks it's saved the file when it really hasn't.

What I do when I'm finished is save with Ctrl+S, then click the X to close, and click "Exit Now" in the dialog if there are no unsaved changes. But sometimes "Save" won't be checked, as if there are no unsaved changes, but in reality the save had failed or something and the file wasn't written to (Windows' "Date Modified" shows the time of a save, but not the most recent one). This means it won't tell me that there are no unsaved changes, making me think it's safe to close.

One time I even caught it as it was happening. Before I closed JOSM, I checked the date modified on my .osm file, and indeed it hadn't saved. Opening this older version in a separate JOSM window shows the file lacking my most recent changes, proving that it isn't being saved properly. I did Ctrl+S again, and that time it did save successfully.