Leaks/Status Meetings/2007-November-20

Agenda

Tomcat still running tests and putting results here.
We need to get bugs filed and assigned. Figure out which block community testing.

Stuart testing different allocators.
We're going to put some content objects into arenas to reduce fragmentation. (nodes, child/attribute lists, text).
Can layout put more objects into arenas?
Javascript is being worked on. Stuart has a patch that moves js objects into separate heap.
Other areas?

plugin GetURL/PostURL leak bug 273025. Doesn't seem important and fix would be very risky.
XPConnect leak in bug 401345, maybe singleton (using the testcase multiple times, different domains, leaks ~250K). FIXED

Get leak monitoring as an extension so that QA can test for leaks during litmus.
- AI:cbarrett Look into OS leaks on mac. (bug 401677)
Improve tinderbox tests.
- Need to measure leaked GDI/user/kernel handles on windows (bug 397854). Possibly show on tinderbox.
- AI:sicking Do leak monitoring while running tinderbox tests.
  - We do want to run trace-refcnt, trace-malloc on reftest/mochitest. (bug 397724)
  - Ideally we'd shut down between each testcase to identify where leaks happen. Mostly useful until we reach 0, but would help with regressions too.
- Want a separate test suite that tests for assertions, crashes, leaks. (bug 397725)
Important leak bugs:
- bug 398292 tracks bugs that make it difficult to find other leaks through fuzzing.
- bug 402335 tracks bugs found through litmus testing.
Finding leaks in extensions
- Need to solve license issue
CoScripter Leak regression suite

AI:sicking Look into enabling trace-refcount, without the tracing part in nightlies.
AI:cbarrett Look into OS leaks on Mac.
AI:dbaron Make assertions fatal on new windows leak box.
AI:sicking Test leaked handles on windows manually using purify.
AI:sayrer Run leak buster while looking for trace-malloc leaks.
AI:sicking to go through and prioritize leak bugs

Tinderbox tests coming along. Coop porting code from tinderbox to buildbot
Tomcat's been busy with release testing so not much new to report.
- We should test content handling again since a big leak there has been fixed.
Check with Sayrer what the status of LeakingPages is. Is it up to date?
Get bugs filed on things that would hinder community leak testing and mark them as blocking?
Merging leak meeting with performance meeting sounds like it would work.