46183 - xul cache should have a pragma no-cache

Status: RESOLVED WONTFIX

(Core :: XUL, defect, P3)

Description

[Doug Turner (:dougt)]

There are some xul dialogs that are only used once in the entire product.  Most 
of the time the developer of this xul knows this.  A case of this is the profile 
picker.  It is run once, and never again used.  There is really no reason to 
cache its prototype.

I was thinking that we should have a way to allow the developer to hint to any 
cacheing subsystems that the current xul files are not to be cached.

Comment 1

[Chris Waterson]

Taking bug. N.B. we should analyze footprint after making XUL cache more 
granular (bug 46129) and implementing memory flushers (or whatever) on the 
cache. These may obviate the need for doing this.

Comment 2

[Judson Valeski]

good idea. either allow for this in the XUL itself, or we should allow for it 
programatically so we can deal w/ the instances we *know* will be singletons.

Comment 3

[Chris Waterson]

hyatt dealt with the important issue here, which was getting rid of extra space
occupied by the one-time-only profile dialogs. We now flush the XUL cache once
we load the first profile. Moving to FUTURE.

Comment 4

[Chris Waterson]

...and making nsbeta3-

Comment 5

[basic]

does this only affects xul in chrome:// or everywhere?

Comment 6

[Jan Varga [:janv]]

yes, this only affects XUL in chrome://

Comment 7

[Doug Turner (:dougt)]

this hasn't been looked at for 6+ years.  marking wontfix.