This is a companion bug to bug 640452 and bug 640457. It's about improvements to memory measurements and benchmarking, ie. anything that helps us understand how to reduce memory consumption without actually reducing it. Eg. bugs relating to about:memory, areweslimyet.com, specific measurements that indicate areas of improvement, etc.
Now that we have even shorter release cycles than the originally planned 3 month ones, I've changed this to be about Firefox 5 and on. If this bug gets too unwieldy I'll close it out and start a new one.
Alias: mprof-fx5 → mprof-fx5+
Summary: [meta] improve memory profiling tools for Firefox 5 → [meta] improve memory profiling tools for Firefox 5+
I'm renaming this from "mprof-fx5+" to "mtools-fx5+", to broaden its scope to cover any kinds of tools related to the measuring, tracking and/or reduction of memory usage.
Alias: mprof-fx5+ → mtools-fx5+
Summary: [meta] improve memory profiling tools for Firefox 5+ → [meta] improve memory tools for Firefox 5+
Renaming again to "MemShrinkTools", to reflect the fact that this tracking is for the MemShrink project.
Alias: mtools-fx5+ → MemShrinkTools
Summary: [meta] improve memory tools for Firefox 5+ → [meta] improve memory tools as part of the MemShrink project
Does anyone care if we close this bug? I certainly wouldn't.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.