From:  Eric Rahm <erahm@mozilla.com>
Date:  19 May 2016 05:44:40 Hong Kong Time
Newsgroup:  news.mozilla.org/mozilla.dev.memory
Subject:  

Re: MemShrink Pre-Triage (17th May 2016)

NNTP-Posting-Host:  63.245.214.181

Notes inline, basically everything is ni. I suggest we skip the meeting today unless there are any items on the agenda.

-e

On Tue, May 17, 2016 at 5:48 PM, Eric Rahm <erahm@mozilla.com> wrote:

MemShrink triage: 2016-05-17

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

5 bugs to triage

  • 1266915 - Core :: DOM - twitter leaks a lot of orphan nodes through window refresh

    Votes:

    Closed WFM.

  • 1272078 - Core :: DOM - Leak of dom/memory-file-data entries persists after disabling addon

    Votes:

    ni'd khuey to see what the status is.

  • 1272979 - Firefox :: Untriaged - FireFox 46 leaking memory

    Votes:

    ni, but user is not accepting ni requests. Posted comment, suggest closing next meeting if no answer.

  • 1273024 - Core :: Layout - [e10s] loading https://500px.com/popular and clicking a photo causes Nightly to hang/use large amount of memory, round 2

    Votes:

    Sounds kind of bad, currently waiting for regression window. Maybe wait for that to come back.

  • 1273206 - Core :: WebRTC: Audio/Video - enumDev/gUM starts RTP thread in 5ms loop

    Votes:

    P3. Fix pending, no indication of amount of memory saved.


There was one more bug that snuck in:

Bug 1270298 - OOM crash on code.org tutorial running in a VM


This is yet another ni on the reporter for a useful memory report.