93561 - Cache is not being created (for a new profile; as of 8/03 builds)

Status: RESOLVED FIXED

(Core :: Networking: Cache, defect)

Description

[John Morrison]

Overview Description: 

The 'Cache' folder is not being created for a profile if it does
not exist. This is true for the creation of a new profile, or for
running with an existing profile from which the Cache folder has
been manually deleted (as a test).

This applies to both commercial and mozilla builds (i.e., this is 
not tied to bad Activation fu). This has been reproduced on two 
different Macs, and on win2k [I haven't tried Linux yet, but I 
expect it's the same deal].

Steps to Reproduce: 
1) Start mozilla -profilemanager with 8/03 build (or use the droplet
   for Profile Manager on Mac)
2) Create a new profile (note: the first panel of the profile manager
   may be blank; if so, hit cancel, then try again. Should work second
   time through)
3) Cancel through activation (if commercial build), and get to the 
   browser startup page. Browse a few pages for extra certainty that
   the Cache should have been created. Shutdown/startup again. Browse
   more. ...

Actual Results: 
  1) Look in profile directory: no 'Cache' folder.
  2) do 'about:cache': only a mem cache device is shown; no disk cache 

Expected Results: 
  Cache (re)created if it doesn't exist (for default prefs, etc.)

Reproducibility: 100% mac/win2k

Build Date & Platform Bug Found: 20010803nn win2k and Mac, comm./moz builds

Note: running with no cache results in some unexpected results in the 
page load timing tests (e.g. kinda like March 22/23)

Comment 1

[John Morrison]

This bug also applies to Linux 8/03 build.

And, it's not just the (re)creation of the cache that is not working. The 
cache is not being used at all. For example, using an existing profile which
has the cache created, with the 8/03 builds mac/linux/win32, no new files are
placed in the cache when loading new pages.

Comment 2

[selmer (gone)]

This is a serious regression, any progress?

Comment 3

[gordon]

I'm working on it.  I'll have a more complete status update later today.

Comment 4

[gordon]

It appears that bug 94349 is preventing the cache service from receiving the
profile-after-change notification it needs to properly initialize the disk cache.

Comment 5

[John Morrison]

This is working (cache is created) in my cvs build pulled last night. I assume
that this is working the comm. verification builds, and I will check in a 
while.

Comment 6

[John Morrison]

The cache is back 
I hit the sack
I've been too long I'm glad to be back
Yes, I'm let loose 
From the noose
That's kept me hanging about


mac/linux/win32 08/10 comm. verif. builds.