From:  Eric Rahm <erahm@mozilla.com>
Date:  05 Oct 2017 02:19:29 Hong Kong Time
Newsgroup:  news.mozilla.org/mozilla.dev.memory
Subject:  

MemShrink Triage (4 Oct 2017)

NNTP-Posting-Host:  63.245.214.181

Lets just do this by email this week.

MemShrink triage: 2017-10-04

Triage URL: http://mzl.la/1yYeaGL

Agenda

(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

    Votes:

    erahm, what do you think?

  • 1398359 - Firefox :: General - Mozilla Firefox Memory Leaking Issue on 64 Bit Builds For No Absolute Reason

    Votes:

  • 1401764 - Testing :: General - Reduce content process leak threshold to 0

    Votes:

    mccr8, what do you think?

  • 1402019 - Toolkit :: Add-ons Manager - browser-addons.js can leak browser.xul window via showInstallConfirmation

    Votes:

  • 1404759 - Firefox :: Untriaged - Firefox memory leak/overly high allocation per tab for some pages/sites

    Votes:

  • 1404936 - Core :: Identity - KeyPair Sign threads are leaked on every use of the feature

    Votes: