238405 - nsXULPrototypeCache doesn't deal with profile-switches

Status: NEW

(Core :: Layout, defect)

Description

[Benjamin Smedberg]

I'm pretty sure the XUL prototype cache doesn't check for profile switches. I'm
confused how it's supposed to work in the case when we start with the
profile-manager (and no XUL.mfasl is available), then we select a profile. Are
we supposed to use a fastload cache in that case?

Can we safely switch the fastload cache on a profile-switch? When is the
fastload cache supposed to be written?

Comment 1

[Brendan Eich [:brendan]]

>  I'm confused how it's supposed to work in the case when we start with the
> profile-manager (and no XUL.mfasl is available), then we select a profile. Are
> we supposed to use a fastload cache in that case?

Sure, and that used to work -- I trust it still does.  The XUL code tries to
create the FastLoad file in the profile directory, and that will fail soft if no
profile has been selected yet.  But for each burst of master XUL document loads
that overlap one another pseudo-concurrently, the code will try again to read
from  or (failing that) write to, or update, the current profile's FastLoad file.

Yeah, something needs to handle profile switching.

/be