1535181 - Possible case where the startup cache isn't purged when it should be

Status: NEW

(Toolkit :: Startup and Profile System, enhancement, P3)

Description

[Robert Strong (they/them - no direct email)]

I noticed that the compatibility.ini file is located in the Windows roaming profile and the startup cache is located in the Windows local profile. I don't know the startup cache code well enough to know for certain but it seems that if a client with a roaming profile updated and then used that roaming profile on another system that had already been updated the profile's compatibility.ini would report it as compatible but the users startup cache in the Windows local profile would be for the old version and not be purged.

Comment 1

[Robert Strong (they/them - no direct email)]

Aaron / Matt - could one or both of you take a look and confirm whether what I described in comment #0 is correct? Thanks!

Comment 2

[Molly Howell (she/her) (no longer active)]

As far as I know that's correct, yes.

I'm having a look through the startup cache files, and I don't really know what I'm looking at, but I can see a few files that have a build ID in their headers. Most don't though; it seems like most of the time we're going off the compatibility.ini check and invalidating the cache only if it doesn't match the running build.

Comment 3

[(No longer employed by Mozilla) Aaron Klotz]

My understanding is the same as Matt's.