From:  Andrew McCreight <>
Date:  11 Feb 2016 03:59:10 Hong Kong Time

Re: MemShrink Pre-Triage (10th Feb 2016)


On Wed, Feb 10, 2016 at 11:23 AM, Eric Rahm <> wrote:

MemShrink triage: 2016-02-10

Triage URL:


(Add name and topic to discuss here)

Bug List

Vote for:

  • P1 High importance, will follow up periodically
  • P2 Important issue, possibly already being worked on
  • P3 Real issue, someone will get to it if they have time
  • moreinfo We need logs, or clarifying information
  • invalid Misclassified, remove the MemShrink tag

14 bugs to triage

  • 873163 - Core :: DOM - Memory leak in window-based workflow due to Vimperator extension


    mccr8, njn, what do you think?

I think this is P3 because it is an issue with an addon. It can probably be moved to evangelism. I need to put together something coherent and post it in the Vimperator issue tracker. It would be cool if we could automatically squash these kinds of leaks, but it isn't obvious how to do that. 
  •  1242861 - Firefox :: Untriaged - Google Inbox slow and cpu intensive

I removed the MemShrink tag. There's not any indication in the bug yet that memory is involved.
  • Votes:

  • 1243949 - Core :: XPCOM - Failure to create a bloat log in a debug build should turn the tree orange


    froydnj, mccr8, what do you think?

P1. This is kind of a fallback that will detect if we are failing to generate leak logs.

  • 1243998 - Core :: DOM - Leak with accessibility, document.fonts, and geolocation prompt in background


    khuey, mccr8, what do you think?

P2 I guess.
  • 1244841 - Core :: JavaScript Engine - Memory consumed by SharedArrayBuffer-based asm.js pages is overreported in about:memory.


    mccr8, what do you think?

  • 1247025 - Core :: Graphics - [e10s] Various Windows-specific content process graphics leaks


    mccr8, what do you think?

P1, though it kind of overlaps with another bug. We're leaking a bunch of random graphics stuff in child processes in e10s, which we're planning to ship soon-ish. Some of it is likely just singletons not being torn down correctly, which is okay, but there's some textures and other things in there that could result in unbounded leaks.


dev-memory mailing list