Performance/MemShrink/Meetings/2011-07-26

Meta

How do we progress next? Will we continue having these weekly meetings forever?

• jst: Once the big issues are sorted out, and we're confident that we're catching regressions, we won't need to meet as much.

Preventing regressions

• Automated tests - https://bugzilla.mozilla.org/show_bug.cgi?id=633670
• More memory reporters - https://bugzilla.mozilla.org/show_bug.cgi?id=563700

Announcements

• New version of jemalloc has introspection abilities! pbiggar & khuey will figure out this week or next whether it can be used anywhere.
• DOM memory reporters: let's test them on pages with huge DOMs
• strongparent patch just landed, and could cause or expand leaks. It makes us rely more heavily on the cycle collector. Be on the lookout for regressions. https://bugzilla.mozilla.org/show_bug.cgi?id=335998
• Removal of clearScope (https://bugzilla.mozilla.org/show_bug.cgi?id=637099 ) - peterv has at least one more leak to fix before this can land
• Cycle collector static analysis. Currently testing the analysis on an old tree, to see if it catches the bugs found by the strongparent and clearscope changes. https://bugzilla.mozilla.org/show_bug.cgi?id=423032

Triage unprioritized bugs

Bug list - 20 bugs

• What should https://bugzilla.mozilla.org/show_bug.cgi?id=435915 morph into?