From:  Eric Rahm <>
Date:  05 Oct 2017 05:59:50 Hong Kong Time

Re: MemShrink Triage (4 Oct 2017)


On Wed, Oct 4, 2017 at 11:19 AM, Eric Rahm <> wrote:

Lets just do this by email this week.

MemShrink triage: 2017-10-04

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

6 bugs to triage

  • 1386177 - Firefox :: Extension Compatibility - Very high memory usage after watching many HTML5 movies on Firefox with uBlock Orgin, even after closing them all


    erahm, what do you think?

ni? on myself, it's not clear how bad this is.
  • 1398359 - Firefox :: General - Mozilla Firefox Memory Leaking Issue on 64 Bit Builds For No Absolute Reason


Closed, ni? for 25 days.
  • 1401764 - Testing :: General - Reduce content process leak threshold to 0


    mccr8, what do you think?

P1? It would be nice to get this to zero.
  • 1402019 - Toolkit :: Add-ons Manager - browser-addons.js can leak browser.xul window via showInstallConfirmation


P3? I don't think anyone is going to fix this.
  • 1404759 - Firefox :: Untriaged - Firefox memory leak/overly high allocation per tab for some pages/sites


 ni? for memory report.
  • 1404936 - Core :: Identity - KeyPair Sign threads are leaked on every use of the feature


P3. If I'm understanding correctly, we leak a thread on shutdown. ni? on jesup for a better summary.