Closed Bug 1111948 Opened 5 years ago Closed 5 years ago
Fix --disable-startupcache, and re-disable the startup cache on B2G in the process
Bug 988880 disabled the startup cache on B2G, because it's not useful and takes up memory. It landed in April. Just one week later, bug 999631 tweaked the mechanism used to disable the startup cache by adding --disable-startupcache. But this option has two defects. - There's no AC_DEFINE(MOZ_DISABLE_STARTUPCACHE). - Even if there was, the relevant #ifdef uses MOZ_DISABLE_STARTUP_CACHE, which has an extra '_' and so will never match. This means that the startup cache is always enabled. Pro-tip: when you add a new configuration option, test that the non-default option works before you land it.
I tested this in the following configurations: - Desktop, normal: startup cache is enabled - Desktop, with --disable-startupcache: startup cache is disabled - B2G: startup cache is disabled
Oops, sorry about that. It is frightening to see that we can regress memory usage so badly without any report :/
Comment on attachment 8536954 [details] [diff] [review] Fix --disable-startupcache, and re-disable the startup cache on B2G in the process Sorry, I should have caught that in review.
Attachment #8536954 - Flags: review?(mshal) → review+
Bug 989373 indicates that this has a very big impact on builds with de-merged compartments. What is the memory impact of this bug on the devices we ship?
> What is the memory impact of this bug on the devices we ship? With system compartment merging on, the startup cache took up 180 KiB for the two runs I did yesterday on my Buri.
Status: ASSIGNED → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 37
Product: Firefox → Core
Target Milestone: Firefox 37 → ---
You need to log in before you can comment on or make changes to this bug.