This report is based on following thread: https://groups.google.com/d/topic/mozilla.dev.platform/IT4SUHyiYeE/discussion The process of getting the CC heap log and doing analysis is painful - you need to generate a text file, open in an editor, search in it, use further scripts for analysis, etc. (it's simple to kill several hours even with a simple scenario/STR how to repro the actual problem) There is no way how to iterate entire CC heap graph from JS. Such APIs, would allow dynamic creation and analysis of the heap and safe a lot of time. Ideally, this could be also used to create an automated test for memory-regression leak bugs in extensions. Honza

Doing this for the JS heap will be more difficult, unfortunately. The CC is already set up with a way to easily plug in other dumping tools. It would be fairly easy except that it isn't safe to call into JS during a CC, so we'll have to write something in C++, then copy it over. They should probably be separate bugs eventually.

bug 726346 is going to expose CC graph dumping to JS, so let's just make this bug about JS heap dumping.