Confirm
396
edits
Changes
m
→Pushing This Forward: link CrashKill and CritSmash, use {{bug}} template
== Pushing This Forward ==
nnethercote and jmuizelaar have volunteered to co-lead the MemShrink effort.
MemShrink could be modelled on [[CrashKill ]] and [[CritSmash]]. One problem with that is that neither nnethercote nor jrmuizelaar are in Mountain View -- jmuizelaar is in the Toronto office (not too bad), nnethercote works at home in a PST+17/+19 timezone. So having CrashKill/CritSmash-style meetings will be difficult.
The MemShrink effort can also include leaks and quasi-leaks in its jurisdiction, even if areweslimyet.com doesn't demonstrate them.
In terms of tracking bugs, now that we're on a 3 month release cycle, I like the idea of having one meta-bug tracking all memory use reductions for the next release. I personally find meta-bugs like this to be quite useful so long as they have a clear end-point. So I opened three bugs:
* [https://bugzilla.mozilla.org/show_bug.cgi?id=640452 {{bug |640452] }} for leaks in Firefox 5* [https://bugzilla.mozilla.org/show_bug.cgi?id=640457 {{bug |640457] }} for other memory use reductions in Firefox 5* [https://bugzilla.mozilla.org/show_bug.cgi?id=640791 {{bug |640791] }} for improvements to memory profiling in Firefox 5
== Other Ideas ==
