Leaks/Status Meetings/2007-October-30: Difference between revisions
< Leaks | Status Meetings
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 34: | Line 34: | ||
== To Do == | == To Do == | ||
* Get leak monitoring as an extension so that QA can test for leaks during litmus. | * Get leak monitoring as an extension so that QA can test for leaks during litmus. | ||
** '''AI:cbarrett''' Look into OS leaks on mac. | ** '''AI:cbarrett''' Look into OS leaks on mac. ({{bug|401677}}) | ||
* Improve tinderbox tests. | * Improve tinderbox tests. | ||
** Need to measure leaked GDI/user/kernel handles on windows ({{bug|397854}}). Possibly show on tinderbox. | ** Need to measure leaked GDI/user/kernel handles on windows ({{bug|397854}}). Possibly show on tinderbox. | ||
Revision as of 17:35, 30 October 2007
Agenda
Tinderbox tests
- Status for tinderbox tests.
QA testing debug builds
- Tomcat ran some 600 litmus tests with leakmonitoring turned on and found lots of leaks. Log here
- bug 102229 seems to be showing up in every log.
- Need a plan to get better debug info, such as refcount traces or smaller steps to reproduce.
- Tomcat to do demo for rest of QA during "work week"
- Which platforms are working?
Status on found leak bugs
- Peter's cycle collection changes bug 379718
- RDF bug 383939
- plugin GetURL/PostURL leak bug 273025
- java leak bug 324796
- DNS shutdown leak bug 102229
- XPConnect leak in bug 401345, maybe singleton (using the testcase multiple times, different domains, leaks ~250K)
- Get bugs filed on bad LeakingPages leaks.
- Linux shutdown leaks now that bug 394466 is fixed?
- Other bad leaks?
Leak test day
- What bugs do we want fixed first?
- What debug info can we get, do we need?
Fixed bugs
- 6 leaks resolved since last week [1]
- First patch for bug 379718 landed.
To Do
- 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.
- 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 tracks bugs that make it difficult to find other leaks through fuzzing.
- bug 394052 Seems to be the only remaining window/document/docshell leak in Mochitests on at least some platforms, possibly all of them.
- Finding leaks in extensions
- Need to solve license issue
- CoScripter Leak regression suite
Action Items
- 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.