122085 - bookmarks.html prefs.js reset on startup/exit

Status: RESOLVED DUPLICATE of bug 92919

(SeaMonkey :: Bookmarks & History, defect)

Description

[Jared Roberts]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.7) Gecko/20020121
BuildID:    0.9.7 (20020121)

Mozilla 0.9.7 (20020121)
(Debian package: 2:0.9.7-5)

Closed Mozilla under high system load, and reopened it and discovered that all
my bookmarks were gone, and my preferences were all reset.  I've found similar
bugs on bugzilla but none of them are recent-- regression?

I didn't change/add any bookmarks or preferences during the entire session. 
Looking at file timestamps, I think the erasure happened during startup, not
shutdown, but I can't be sure.  My history was somehow left intact.

The problem is not reproducable, I've used this build several times before
without incident, and I cannot reproduce it now.  My guess is that it was
related to the high system load.  The only unusual thing I noticed is that the
mozilla throbber in the upper-right was empty--  there was just a box where it
should have been, but I could see the toolbar behind it.  So something may have
already been quite amiss.

Reproducible: Couldn't Reproduce
Steps to Reproduce:


As a Debian package, this may not be a standard mozilla build.  I believe
several patches from bugzilla have been applied-- the maintainer is Takuo KITAME
<[e-mail]>.  I'm filing a bug with him as well.

Comment 1

[Sören 'Chucker' Kuklau (gone)]

I know it sounds silly, but perhaps you changed the files to read-only? That
would cause exactly this effect, but _then_ it would be reproducible.

Comment 2

[Jared Roberts]

No, everything was read/write

Comment 3

[Chris Lyon]

Jared, are you still seeing this with a recent build?

Comment 4

[Jared Roberts]

I only saw it the one time and it wasn't reproducible-- I'm thinking *maybe* the
drive was full and when the write failed it just hosed everything.  The "high
load" I mentioned was htdig running in the background and thrashing the disk
like crazy-- I know there was some space at the end of the run, but it may have
been full when I closed the browser.  I still don't think so, but since nobody
else can get the "bug", I'm willing to concede it might have just been that.

Comment 5

[Chris Lyon]

It may have been bug 92919.  I'll dupe it as that for now.  If you get any new 
information, please reopen.

Thanks!

*** This bug has been marked as a duplicate of 92919 ***