Closed Bug 172245 Opened 23 years ago Closed 22 years ago

System shut down while prefs.js file is being written, causes prefs.js file to be corrupt

Categories

(Core Graveyard :: QuickLaunch (AKA turbo mode), defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 132517

People

(Reporter: esther, Assigned: law)

Details

Using branch build 20020925 on winxp trying to reproduce a reported case of Profile not seeing mail accounts, address books and bookmarks when relaunching after a system crash I found this can happen if the timing is right. Comment from Susie Wyshak: This just happened to me on 9/23 commercial branch build on Win2K I had closed down without shutting down. I tried launching the build upon starting up. Nothing happened so I clicked the icon again. Nothing. So I went to see if there were processes running and there were 2 running. So I ended one. Then the browser started up with no profile :-(((((( I'm not sure of all the times we write to the prefs.js file, but 12 tries, my prefs.js file lost pointers to mail, address books 5 times, resulting in a Profile that was basically default. My test is to basically do a system shut down by turning off the power (similiar to a system crash that doesn't shut down nicely which is what happened to Susie) when: 1. NS7 is up QL is enabled but I am not doing anything at the time =no problem 2. NS7 is up, QL not enabled and I just changed a Preference then OK'd the dialog = no problem 3. NS7 is up, QL enabled and I just changed a Preference then OK'd the dialog = prefs.js file is corrupt giving configuration error in line 443 or at 1 byte.
I haven't tested our original tests for bug fix 155080 with the 9-25 branch build to see it that scenario causes the problem, I can check that tomorrow. Again, this newly reported bug included a system crash and shutdown while NS7 was up and running. Also, in all the testing today I never saw 2 instances of Netscape running in the task manager when rebooting and launching NS7.
Same Problem for me with mozilla 1.1 on Linux without quicklaunch. The prefs.js is completely destroyed during a abnormal system shutdown. I had it now the 3. time on to different Pc`s.
I've also had this happen to me (several times), running 1.1 on WinXP. A few of the times, the system never crashed, I just shut down as normal and when I turn on the computer the next day, *POOF* all accounts and settings are gone (the prefs.js AND the prefs.bak have been reset). Until fixed, there is a quick trick to protect yourself. When you have Mozilla all set up and working normally, make a copy of the prefs.js file as a backup somewhere else on your computer. If your settings reset again, simply replace the default prefs.js that comes up with the one you've saved as a backup. Your settings and accounts should reappear.
Dupe. *** This bug has been marked as a duplicate of 132517 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
verified
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.