Yes it is. I also wrote more about the backend implementation on lobste.rs &lt;<a href="https:&#x2F;&#x2F;lobste.rs&#x2F;s&#x2F;cvtz0x&#x2F;firefox_s_new_memory_tool" rel="nofollow">https:&#x2F;&#x2F;lobste.rs&#x2F;s&#x2F;cvtz0x&#x2F;firefox_s_new_memory_tool</a> &gt;:<p><i>Hi folks,<p>For the last year or so, my coworker Jim Blandy and I have been designing and implementing APIs in SpiderMonkey (Firefox’s JavaScript engine) to support various kinds of memory allocation&#x2F;retention introspection. We are finally shipping a frontend to users as well, and this blog post is an intro to that. This is very much the tip of the iceberg and we wanted to just start shipping since we’ve been building APIs for so long, but this is really a fraction of the things planned. Nightly already has filtering&#x2F;searching and will soon have import&#x2F;export of snapshots as well as diffing &lt;<a href="http:&#x2F;&#x2F;i.imgur.com&#x2F;qjWOERs.gif" rel="nofollow">http:&#x2F;&#x2F;i.imgur.com&#x2F;qjWOERs.gif</a> &gt;. Dominator trees and shortest paths from GC roots are incoming as well.<p>How is this built?<p>We made an abstraction called “ubi::Node” &lt;<a href="https:&#x2F;&#x2F;dxr.mozilla.org&#x2F;mozilla-central&#x2F;rev&#x2F;a8ed7dd831d1969a5a1a8636e63bd93d6aeaf94a&#x2F;js&#x2F;public&#x2F;UbiNode.h#31-163" rel="nofollow">https:&#x2F;&#x2F;dxr.mozilla.org&#x2F;mozilla-central&#x2F;rev&#x2F;a8ed7dd831d1969a...</a> &gt; (for “ubiquitous node”) that sees the GC’s heap graph with a traditional nodes-and-edges view so that we don’t have to worry about the difference between (say) an object and some jit code when writing graph analyses. What is cool is that this interface can be backed by either the live heap graph or an offline heap graph. When you save a heap snapshot, we traverse this graph and serialize it into protobuf messages. These can then be reconstructed into an offline graph which you can run analyses on at your leisure.<p>We also make pretty extensive use of stack capturing, because that is a concrete way to tie retention and GC pressure back to something that feels concrete to users: locations in their source code. I’ve written a bit about how we minimize the overhead of (potentially very frequent) stack captures before by hash consing individual frames so that tails are shared &lt;<a href="http:&#x2F;&#x2F;fitzgeraldnick.com&#x2F;weblog&#x2F;61&#x2F;" rel="nofollow">http:&#x2F;&#x2F;fitzgeraldnick.com&#x2F;weblog&#x2F;61&#x2F;</a> &gt;. Since then, we have also found a neat way to avoid walking the stack repeatedly if we have already done so once.<p>If anyone has any questions, please ask away :)</i><p>And I made a quick update:<p><i>Also, Jim loved writing this comment so much (it is a fun read) that I feel I have to share it :)<p><a href="https:&#x2F;&#x2F;dxr.mozilla.org&#x2F;mozilla-central&#x2F;rev&#x2F;a8ed7dd831d1969a5a1a8636e63bd93d6aeaf94a&#x2F;mfbt&#x2F;FastBernoulliTrial.h#18-172" rel="nofollow">https:&#x2F;&#x2F;dxr.mozilla.org&#x2F;mozilla-central&#x2F;rev&#x2F;a8ed7dd831d1969a...</a><p>We use this for sampling object allocations to give insight into GC pressure.</i>