Closed Bug 203188 Opened 21 years ago Closed 21 years ago

System crash when mozilla open erases all preferences and Bookmarks

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 193749

People

(Reporter: daniel.armbrust.list, Assigned: asa)

References

()

Details

(Keywords: dataloss)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030401

If you have mozilla open, and you crash your computer (say by having an ATI
crash-o-matic video card).  Upon a reboot of your computer, when you launch
mozilla, it has forgotten nearly everything about you.  It gives you a brand new
prefs.js (and the prefs.bak is a binary file filled with 0's), it OVERWRITES
your borkmarks.html with a blank one - AND LEAVES NO BACKUP!!! - but then
strangely, it decides to keep your download history, and your browsing history,
and your url history.  I'm not sure what it does with mail... 

Reproducible: Always

Steps to Reproduce:
1.Open mozilla.
2.Crash your computer (maybe just hitting the reset button will do it)
3.Open Mozilla.


Expected Results:  
NOT ERASED THE PROFILE.
At a minimum, it should not simply overwrite your bookmarks, and it shouldn't
write out the prefs.js file with all 0's.  

I have noticed this since moving into the 1.3+ versions... which seem to crash
often with ATI's **** video drivers.
Keywords: dataloss
Summary: Crash erases all preferences and Bookmarks → System crash when mozilla open erases all preferences and Bookmarks
also resets all email. This bug is reproduceable under XP Pro Version 5.1.2600
Service Pack 1 Build 2600 on a dual Pentium platform.  
dupe of "bookmarks and personal preferences are lost after system crash..."

*** This bug has been marked as a duplicate of 193749 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.