Places.sqlite spontaneously corrupts

[jeffw_00]

Hi - Earlier I had posted an issue about moving places.sqlite between locations. This is not about that. I'm running 2.31. I haven't touch/copied/overwritten or otherwise mucked with places.sqlite (or anything under the hood) for 3-4 days. I startup Seamonkey just now, and all my bookmarks are gone. Fortunately I have another installation, and copying places.sqlite from that location fixed the problem. But this is really bad, I mean, if this file can spontaneously corrupt it can make SM unusable. Unfortunately I can't identify anything I did that might have caused this (really, just browsing and Emailing) so I can't help isolate, but whatever code fixes were made in 2.31 to fix the problems in 2.30, they should be suspect.

Thanks for Listening!

/j

[therube]

Keep an eye out for 30 to 31, Bug 1093623 - Bookmarks are lost when upgrade 2.31b1 from 2.30 .

[jeffw_00]

Thanks therube, but that's not what I'm reporting. I upgraded days ago. it happened days after the upgrade.

[jeffw_00]

This continues to be a problem. I admit that I copy places.sqlite from one installation to the other. But it can work in the destination installlation under heavy use for 5-6 days and then suddenly I open SeaMonkey and all my Bookmarks are G O N E!!!!!!

This is broken guys - please consider improving stability here
/j

[therube]

Are all your Profiles running SeaMonkey 2.31 or greater?
If any are running 2.30, you're subject to run into this.

Are /bookmarkbackups/*.json* being created (& at least some, current)?

[jeffw_00]

Yes - they're all running 2.31 or greater (moved to 2.32 today).
files of the form bookmarks-2015-01-19_549_TWuX3GfDJW-mQxWJZSmR6w==.jsonlz4 are being created. one was created today.