Closed Bug 187327 Opened 22 years ago Closed 22 years ago

Especially after a crash but even after normal exit, cache will get flushed for no reason

Categories

(SeaMonkey :: General, defect)

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 105843

People

(Reporter: dcamp, Assigned: asa)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2.1) Gecko/20021130

My cache is set to 1048576 KB and Never. If I browse around to populate the
cache and then exit mozilla, the cache directory is sometimes emptied on my next
launch. This seems to happen consistently after mozilla or my machine crashes.
In related experience with Netscape 7.01, same cache settings, same problem.
Also in Netscape, I would lose my cookies, history, and MSFs under the same
conditions; Mozilla does not seem to be hosing over my cookies, history, or MSFs.

Reproducible: Sometimes

Steps to Reproduce:
1. Set cache to 1048576 KB and Never.
2. Browse around.
3. Power off machine mid-session.
4. Launch mozilla
5. Inspect cache directory -- prolly empty

Actual Results:  
Got to tranfer pics of my favorite Indian actresses over my modem again.

Expected Results:  
Loaded them from my cache.

I run McAfee.

My computer does crash fairly frequently lately, (although I am actually fairly
convinced that this has been due to Netscape 7.01). Perhaps Mozilla is finding
cache files out of sync with its metadata and deciding to start from ground
zero. If that is the case then that is an unfortunate strategy. The cache should
be managed in such a way that the metadata can be rebuilt from valid cached
files so that it is robust despite myriad failures. A cache should never be
cleared except upon the user's demand.
If you are sharing your profile between Mozilla and Netscape then this bug is
invalid. You should use different profiles for each app.
It's normal that the cache is cleared after a crash. That's done on purpose to
make sure the cache not corrupted.

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