How to *stop* fastload cache?

464 views
Skip to first unread message

Manuel Reimer

unread,
Jan 12, 2012, 1:43:10 AM1/12/12
to
Hello,

on Linux it doesn't seem to be a problem but on Windows this "fastload"
makes development *suck*! I have to delete "startupCache.4.little" every
time, I restart my browser to test changes, I did in my addon.

How to get rid of this "feature" completely? So far anything, I needed,
was "nglayout.debug.disable_xul_cache". Now I added
"nglayout.debug.disable_xul_fastload" but this also doesn't stop
fastload. It still is generated and it still caches javascript files.

Why don't you just add a "development mode" pref and if this is on true,
then disable all those show-stoppers.

Yours

Manuel

Jonathan Protzenko

unread,
Jan 12, 2012, 3:21:51 AM1/12/12
to manue...@nurfuerspam.de, dev-ext...@lists.mozilla.org, Manuel Reimer
https://developer.mozilla.org/en/Setting_up_extension_development_environment

In particular: « As of Gecko 2 (Firefox 4), JavaScript files are cached
("fastload"). The -purgecaches command-line flag disables this
behavior. Alternatively, you can set the MOZ_PURGE_CACHES environment
variable. See this bug for more information. »

jonathan
> _______________________________________________
> dev-extensions mailing list
> dev-ext...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-extensions

Manuel Reimer

unread,
Jan 12, 2012, 4:46:02 AM1/12/12
to
Jonathan Protzenko wrote:
> In particular: « As of Gecko 2 (Firefox 4), JavaScript files are cached
> ("fastload"). The -purgecaches command-line flag disables this
> behavior. Alternatively, you can set the MOZ_PURGE_CACHES environment
> variable. See this bug for more information. »

Why is there no preference to disable this?

Why can't there be some "global pref" which just kills all those caches?
Maybe it would be an option to link this with the
"nglayout.debug.disable_xul_cache" pref?

I currently killed this anti-developer feature by just replacing this
"startup cache" file with a zero byte file and dropping write permission
for it. Doesn't seem to cause any problems. Doesn't even seem to have
any effect on startup speed...

Yours

Manuel

Neil

unread,
Jan 12, 2012, 5:04:02 AM1/12/12
to
Manuel Reimer wrote:

> Jonathan Protzenko wrote:
>
>> In particular: « As of Gecko 2 (Firefox 4), JavaScript files are
>> cached ("fastload"). The -purgecaches command-line flag disables this
>> behavior. Alternatively, you can set the MOZ_PURGE_CACHES environment
>> variable. See this bug for more information. »
>
> Why is there no preference to disable this?

Because the startup cache starts up before the preferences do. (And no,
it wouldn't be easy to change that.)

--
Warning: May contain traces of nuts.

Manuel Reimer

unread,
Jan 12, 2012, 5:28:24 AM1/12/12
to
Neil wrote:
> Because the startup cache starts up before the preferences do. (And no,
> it wouldn't be easy to change that.)

Isn't it possible to unload/destroy the cache as soon as the preference
is read successful? Or just don't write it to disk if the pref is set?
If the file is never written or overwritten with a zero byte file, then
loading the cache is no problem.

Yours

Manuel

Reply all
Reply to author
Forward
0 new messages