Confirmed users
716
edits
Leaks/Status Meetings/2007-September-25: Difference between revisions
Jump to navigation
Jump to search
Leaks/Status Meetings/2007-September-25 (view source)
Revision as of 18:00, 25 September 2007
, 25 September 2007no edit summary
(use sections more) |
No edit summary |
||
| Line 6: | Line 6: | ||
* How do we best find and fix remaining leaks. | * How do we best find and fix remaining leaks. | ||
** Need to find more | |||
** Need to find leaks when extensions are installed. | |||
** Chrome leaks, such as download manager, prefs panel? | |||
** '''AI:Jonas''' Look into enabling trace-refcount, without the tracing part in nightlies. | |||
** With OS leaks lower we could enable trace-malloc manually and get more useful data. | |||
*** {{bug|394466}} should fix OS leaks on linux. | |||
*** '''AI:cbarrett''' Look inte OS leaks on mac. | |||
*** {{bug|374822}} Need a windows tinderbox with leak numbers since OS leaks are lower there. | |||
** Need to measure leaked GDI/user/kernel handles on windows. Possibly show on tinderbox. | |||
=== Tools (fixing and finding) === | === Tools (fixing and finding) === | ||
| Line 13: | Line 22: | ||
=== Finding leaks === | === Finding leaks === | ||
* Sayrers leak hunting tool. Do we need to have more people run it? Should we automate? Can we improve it? Is it finding the right types of leaks? | * Sayrers leak hunting tool. Do we need to have more people run it? Should we automate? Can we improve it? Is it finding the right types of leaks? | ||
** {{bug|396368}} Live connect leak the biggest one still not fixed. | |||
** Leaks look like they are real leaks that users run into, though sometimes find small, less important, leaks. | |||
** No automation or broader running needed so far, still finding enough. | |||
* Jesses fuzzing. Does it find useful leaks that normal users would run in to? | * Jesses fuzzing. Does it find useful leaks that normal users would run in to? | ||
** {{bug|102229}} {{bug|397206}}, {{bug|393357}} are remaining bugs. | |||
** Useful because it does testing on new features. | |||
* Do leak monitoring while running tinderbox tests. | |||
** '''AI:sicking''' look into this. | |||
** We do want to run trace-refcnt, trace-malloc on reftest/mochitest | |||
** 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. | |||
* Do we need regression tests? | * Do we need regression tests? | ||
** Want a separate test suite that tests for assertions, crashes, leaks. | |||
* Would extensions that cause GC/CC help? | * Would extensions that cause GC/CC help? | ||