Announcing Memory Tools

[Jordan Santell]

With the release of Dev Edition 44 today, the first version of the
Developer Tools' Memory Tools hits the public![0] The new memory tool helps
front-end engineers better understand and optimize the way pages allocate
and retain memory. The tool works by taking a snapshot of the heap, then
allows you to drill down by retained object type, allocation stack, or
internal representation. There will be a hacks post later this week with an
overview of using this tool with a demo video as well.

We have many things in the pipe planned for this tool[1], like heap
diffing, shortest path from GC root to an object, and dominator tree views
for identifying memory accumulation points. Try it out and be sure to
file[2] any bugs you run into or features that'd help in any memory
debugging.

Shout out to Nick Fitzgerald and Jim Blandy for working on the necessary
platform work **for years**, James Long for his React/Redux guidance, Helen
Holmes for her UX expertise, Victor Porof and Tim Nguyen for last minute
styling sorcery, and everyone else who helped in testing and getting this
landed!

[0]
https://2r4s9p1yi1fa2jd7j43zph8r-wpengine.netdna-ssl.com/files/2015/11/nyanparticles.png
[1]
https://bugzilla.mozilla.org/buglist.cgi?component=Developer%20Tools%3A%20Memory&product=Firefox&bug_status=__open__&list_id=12655709
[2]
https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools%3A%20Memory

[Brian Grinstead]

Congratulations all! Looking forward to using it and to reading the upcoming post.

Brian

> _______________________________________________
> dev-developer-tools mailing list
> dev-devel...@lists.mozilla.org
> https://lists.mozilla.org/listinfo/dev-developer-tools