Closed Bug 240569 Opened 20 years ago Closed 20 years ago

Win XP crashed long after Mozilla closed. WinXP Reboot made Mozilla replace files with defaults erasing data files.

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 193749

People

(Reporter: escaloni, Unassigned)

Details

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.2) Gecko/20040308
Build Identifier: Mozilla 1.6 / Windows XP

Third time this happened to me.   Regardless of what caused it, adding a backup
file will help recover loses.
Windows XP crashed long after using Mozilla.   I lost all critical Mozilla
files, e.g. bookmarks, saved emails, even theme.   Cause is unknown.  But this
is not important.   The files that took months to accumulate disappeared.   I
backed up some of the information but cannot recover everything.  So can you add
an auto-backup-save feature, so the latest copy of those critical files can be
saved elsewhere for recovery.

Reproducible: Couldn't Reproduce
Steps to Reproduce:
No method to reproduce, but I am guessing the following happened.
1.Cacheman, a memory optimizer,  did not allocate enough cache memory somewhere
causing Windows XP to crash.   Mozilla files were not written properly to the
hard disc.
2. Rebooting caused Mozilla to not find data files - since they were corrupt.  
3. Mozilla reloaded default files, erasing the original emails saved, together
with the blank bookmarks, and default theme.

Actual Results:  
n/a

Expected Results:  
If Mozilla could automatically backup the critical data files in a different
location, that could either AUTOLOAD when there are problems, or at least could
be available for manually copying into the correct directory after the files
became corrupt.

Windows XP "blue screened", with no reason for the problem.

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