Changes

Jump to: navigation, search

Performance:Leak Tools

293 bytes added, 06:50, 15 January 2013
no edit summary
To fix a leak, the next step is to figure out why the rooting object is alive. For a C++ object, you need to figure out where the missing references are from. For a JS object, you need to figure out why the JS object is reachable from a JS root. For the latter, you can use the corresponding [https://github.com/amccreight/heapgraph/tree/master/gc find_roots for JS] on the gc-edges file generated by the CC dump.
 
===== Addons for creating and analyzing cycle collector graphs =====
* Simple, ugly, yet rather powerful [https://bugzilla.mozilla.org/show_bug.cgi?id=726346 about:cc]
* Prettier but a bit slower [https://addons.mozilla.org/en-US/firefox/addon/cycle-collector-analyzer/?src=ss about:ccdump]
 
=== Leak tools for medium-size object graphs ===
Confirm
157
edits

Navigation menu