In <news:[email protected]>, NoOp <[email protected]> wrote:
> On 12/26/2014 02:30 PM, »Q« wrote: > > In <news:[email protected]>, > > NoOp <[email protected]> wrote: > > > >> Follow-up: looks like someone already opened a bug report & it got > >> the wishy-washy "RESOLVED WORKSFORME" (aka 'Don't Know, Don't Care) > >> treatment: > >> > >> <https://bugzilla.mozilla.org/show_bug.cgi?id=686237> > >> (places.sqlite-wal and places.sqlite-shm not removed on exit) > >> > >> I reckon it's worth reopening (notice comment #2)... > > > > c2 is an issue with using different SeaMonkeys on different OSes > > with a single profile directory. AFAIK, that's a use case that's > > never been supported, and I'd expect any bug filed about it would > > be marked INVALID or WONTFIX. For anyone sharing a profile across > > multiple OSes, vacuuming the database before each use should > > eliminate the issue. > > Regardless of whether the OP is sharing across multiple OS's, > places.sqlite should close it's temp files on shutdown. According to <https://www.sqlite.org/wal.html>, they're "quasi-persistent", not temporary, files. I don't see any reason on the face of it that they should be deleted when SeaMonkey closes. > No other *.sqlite db's in SeaMonkey exhibit this issue (that I'm > aware of). Re vacuuming... how many users do you reckon actually know > how to do this, or 'Compact Database'? I reckon it's about the same as the number who actually need to know how to do it. _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
