Leaks/Status Meetings/2007-October-9
< Leaks | Status Meetings
Jump to navigation
Jump to search
Agenda
Finding plans
- Schreps posting in moz.dev.performance [1]
- Should we do a CoScripter thing?
Tools (fixing and finding)
- Status for tinderbox tests.
- Should we force CC between page-loads during perf tests?
- Have patch to do CC on command bug 399107.
Status on found leak bugs
- Are there leak bugs filed that are blocking further discovery?
To Do
- Get leak monitoring as an extension so that QA can test for leaks during litmus.
- bug 394466 should fix OS leaks on linux.
- AI:cbarrett Look into OS leaks on mac.
- Improve tinderbox tests.
- Need to measure leaked GDI/user/kernel handles on windows. Possibly show on tinderbox.
- bug 374822 Need a windows tinderbox with leak numbers since OS leaks are lower there.
- 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 396368 Live connect leak the biggest one still not fixed.
- bug 398292 now tracks bugs that make it difficult to find other leaks through fuzzing.
- Finding leaks in extensions
- Need to solve license issue
Action Items
- AI:sicking Look into enabling trace-refcount, without the tracing part in nightlies.
- AI:cbarrett Look inte OS leaks on mac.
- AI:sicking talk with build about setting up a Windows leak test machine (bug 374822.