This looks super useful - thanks Nathan! Tooling like this is critical to helping us get to the bottom of intermittent nastiness.
On Tue, Sep 15, 2015 at 1:32 PM, Nathan Froyd <nfr...@mozilla.com> wrote: > Hi all, > > For some intermittent leaks, it's not at all clear where the leaked objects > are coming from, especially for objects that are widely used across the > codebase. Bug 1196430 added the ability for our leak checking mechanism to > track allocation stacks of objects and to print said stacks for leaked > objects at the end of a test run. > > The wiki page for BloatView has been updated with a description of how to > use this capability: > > https://developer.mozilla.org/en-US/docs/Mozilla/Performance/BloatView#Bloat_Statistics_on_Tinderbox > > If you are facing a particular pernicious intermittent leak, please > consider doing some try runs with --setenv=XPCOM_MEM_LOG_CLASSES=FOO added > to aid in understanding where the leak starts. Also, please feel free to > file bugs on how leak checking could be improved to provide more > information for investigating these kind of bugs. > > Thanks, > -Nathan > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
