On Mon, May 19, 2014 at 5:32 PM, L. David Baron <dba...@dbaron.org> wrote: > > There are some things that I do with trace-malloc that I'm not sure > if the other tools do. > > One is to check for leaks that involve caches (i.e., don't involve > unreachable pointers). One can take two memory dumps at different > times and build a allocation-stack-tree-diff of the two dumps.
It should be easy to modify DMD to emulate this. > Another is being able to find the root strongly connected components > of the memory graph, which is useful for finding leaks in other > systems (e.g., leaks of trees of GTK widget objects) that aren't > hooked up to cycle collection. It's occasionally even a faster way > of debugging non-CC but nsTraceRefcnt-logged reference counted > objects. How does trace-malloc do that? It sounds like it would need to know about object and struct layout. Nick _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
