From:  Eric Rahm <erahm@mozilla.com>
Date:  20 Oct 2016 06:30:22 Hong Kong Time
Newsgroup:  news.mozilla.org/mozilla.dev.memory
Subject:  

Re: MemShrink Pre-Triage (19 Oct 2016)

NNTP-Posting-Host:  63.245.214.181



On Wed, Oct 19, 2016 at 2:20 PM, Eric Rahm <erahm@mozilla.com> wrote:

Small list today, lets just do things online.

MemShrink triage: 2016-10-19

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

4 bugs to triage

  • 1307713 - Core :: General - Firefox operations degrade after reaching 2gb of RAM

    Votes:

    erahm, what do you think?

This one is a bit weird, I have another ni out to the reporter but we're seeing several thousand non-window zones and hundreds of top-level windows. They're on ESR 45 so honestly there's not much we can do code-wise but we can at least see if add-ons etc are contributing to their problems. I'd probably give it a P3.
  • 1309115 - Firefox :: Untriaged - eaten memory in seconds

    Votes:

This is ni? but seems pretty bad. I can attempt to repro on Windows.
  • 1311039 - Core :: Untriaged - about:memory gives a negative response in some areas

    Votes:

 It looks like we're failing to query heap-allocated for this user. Inclined to P3, but maybe it's a wider issue on OSX 10.12?
  • 1311422 - Firefox :: Developer Tools - about:debugging and service worker debugger leak compartments in nightly 52

    Votes:

P2.