Leaks/Status Meetings/2007-October-16: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(New page: « Back to Status Meetings == Agenda == === Tinderbox tests === * Status for tinderbox tests. * kernel, gdi, and user handles leaks {{bug|397854}} === QA ...)
 
 
(2 intermediate revisions by the same user not shown)
Line 43: Line 43:
* '''AI:cbarrett''' Look into OS leaks on Mac.
* '''AI:cbarrett''' Look into OS leaks on Mac.
* '''AI:sicking''' Talk with build about setting up a Windows leak test machine ({{bug|374822}}).
* '''AI:sicking''' Talk with build about setting up a Windows leak test machine ({{bug|374822}}).
== Meeting Notes ==
* Tinderbox tests
** Coop working on getting debug builds up and running on tinderbox.
* Crash-test testsuite
** Code in the tree
** Need to decide on name and directory to put test
** Lets call it crash-test
** Can put tests either spread out like mochitests, or in a central directory like mozilla/testing/crashtest
* Looks like we're not leaking handles, so not as urgent.
** Vlad might have looked into it with other tools.
* Running litmus with debug builds
** '''AI:'''sicking: Talk with build about getting debug builds to QA for litmus testing.
* Leak bugs
** Peter has patch in bug, ready for reviews
*** Fixes fault in CC which would be nice to have in for beta {{bug|386912}}
** Timer leaks {{bug|330128}}, {{bug|387341}}
*** If we fix {{bug|330128}} we might not need to do {{bug|387341}}.
*** Threading issues, and doesn't help C++ callers
** Need more info on what's leaking to help with {{bug|387203}}. '''AI:'''Peterv to help out.

Latest revision as of 23:04, 19 October 2007

« Back to Status Meetings

Agenda

Tinderbox tests

  • Status for tinderbox tests.
  • kernel, gdi, and user handles leaks bug 397854

QA testing debug builds

  • Status?

Status on found leak bugs

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 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:sicking Talk with build about setting up a Windows leak test machine (bug 374822).

Meeting Notes

  • Tinderbox tests
    • Coop working on getting debug builds up and running on tinderbox.
  • Crash-test testsuite
    • Code in the tree
    • Need to decide on name and directory to put test
    • Lets call it crash-test
    • Can put tests either spread out like mochitests, or in a central directory like mozilla/testing/crashtest
  • Looks like we're not leaking handles, so not as urgent.
    • Vlad might have looked into it with other tools.
  • Running litmus with debug builds
    • AI:sicking: Talk with build about getting debug builds to QA for litmus testing.
  • Leak bugs
    • Peter has patch in bug, ready for reviews
      • Fixes fault in CC which would be nice to have in for beta bug 386912
    • Timer leaks bug 330128, bug 387341
      • If we fix bug 330128 we might not need to do bug 387341.
      • Threading issues, and doesn't help C++ callers
    • Need more info on what's leaking to help with bug 387203. AI:Peterv to help out.