I skipped the last MemShrink report due to Christmas, so we have four weeks’ worth of bug fixes today.<\/p>\n
Joe Walker fixed a bad leak<\/a> found by Jesse Ruderman:\u00a0 if you closed a browser window with the developer toolbar open it would leak “everything”.\u00a0 This was a MemShrink P1 bug.<\/p>\n Anton Kovalyov fixed a leak involving scratchpad<\/a>.\u00a0 This bug was also found by Jesse Ruderman.<\/p>\n Randell Jesup fixed some WebRTC leaks<\/a>.<\/p>\n John Schoenick fixed a leak involving plugins<\/a>.<\/p>\n Josh Aas fixed a leak in some networking code<\/a>.<\/p>\n I wrote a more detailed blog post about DMD<\/a>.\u00a0 Here is the take-away message.<\/p>\n about:memory is MemShrink\u2019s not-so-secret weapon when it comes to understanding Firefox\u2019s memory consumption… and DMD is how we make about:memory better.<\/p><\/blockquote>\n Lots of under-the-hood improvements have been made to DMD since I wrote that.\u00a0 Users on Mac, Linux and B2G who aren’t afraid of doing their own builds should try it out<\/a>.\u00a0 Also, Ehsan Akhgari got it to build on Windows<\/a>, though it’s not yet clear how well it works on that platform.\u00a0 If anyone wants to try it out, please let me know how it goes.<\/p>\n Ben Turner made the workers memory reporter be able to handle workers that use ctypes<\/a>.\u00a0 This was important, especially on B2G, because each process can have one or two or more such workers — this is for Firefox chrome stuff, not web content — and we weren’t measuring them at all, and they can take multiple MiB each.<\/p>\n I fixed the orphan DOM node memory reporter<\/a>.\u00a0 The introduction of WebIDL had changed the layout of some paired JS\/DOM objects, and such objects weren’t being reported.\u00a0 (DMD discovered the unreported memory, and Boris Zbarsky helped me interpret what it meant.)\u00a0 I see this accounting for multiple MiB of orphan nodes when using Gmail.<\/p>\n I added a memory reporter for the event listenener manager’s hash table<\/a>.\u00a0 It starts off small, but I’ve seen it go as high as 1.5 MiB after lots of browsing.\u00a0 (DMD helped me identify this too.)<\/p>\n Kartikaya Gupta added a memory reporter for graphics textures on Android<\/a>.<\/p>\nDMD<\/h3>\n
Memory Reporters<\/h3>\n