Leaks/Status Meetings/2007-November-13

From MozillaWiki
Jump to: navigation, search

« Back to Status Meetings

Agenda

Tinderbox tests

  • Status for tinderbox tests.

QA testing debug builds

  • Tomcat is testing chrome for leaks and putting up logs here
  • Tomcat to do demo for rest of QA during "work week"

Fragmentation

  • Stuart has done testing here
  • Opening a set of pages and closing them brings memory usage up 11.4MB to 30MB. 4.6MB of that is additional used memory, 13.8MB is fragmentation.
  • What is the extra 4.6MB?
  • What can we do about fragmentation.

Status on found leak bugs

Fixed bugs

  • 30(!!) leaks resolved since last week. [1]
  • 18 resolved as FIXED

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.
    • 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.
  • AI:sayrer Run leak buster while looking for trace-malloc leaks.

Meeting Notes

  • Tinderboxes waiting for IT to set up hardware
  • Tomcat is doing UI testing. Finding lots of bugs. Will start filing in bugzilla so we can get them fixed.
  • Seeing lots of fragmentation.
    • Same cross platform
    • Arrays are causing churn. Patches written for some of it.
    • Javascript causing a lot of noice. Testing to put JS stuff in its own heap.
    • Vlad has tool that is able to replay malloc patterns based on dtrace.
    • Windows has low fragmentation heap. Makes us fragment a lot less, but makes memory usage goes up.
    • We should try to put objects that have similar lifetime and used together into arenas.
    • Won't be able to get everything into arenas, but hopefully the hotspots.
  • Bad JS pattern of calling GetService and caching the service in the global object.
  • AI:sicking to go through and prioritize leak bugs
Retrieved from "https://wiki.mozilla.org/index.php?title=Leaks/Status_Meetings/2007-November-13&oldid=74281"