From:  Eric Rahm <erahm@mozilla.com>
Date:  18 May 2016 08:48:09 Hong Kong Time
Newsgroup:  news.mozilla.org/mozilla.dev.memory
Subject:  

MemShrink Pre-Triage (17th May 2016)

NNTP-Posting-Host:  63.245.214.181

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:

    mccr8, what do you think?

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

    Votes:

    khuey, what do you think?

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

    Votes:

  • 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:

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

    Votes: