From:  Eric Rahm <erahm@mozilla.com>
Date:  03 Nov 2016 06:55:53 Hong Kong Time
Newsgroup:  news.mozilla.org/mozilla.dev.memory
Subject:  

Re: MemShrink Pre-Triage (2 Nov 2016)

NNTP-Posting-Host:  63.245.214.181



On Wed, Nov 2, 2016 at 3:37 PM, Eric Rahm <erahm@mozilla.com> wrote:

MemShrink triage: 2016-11-02

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

  • 1298905 - Core :: JavaScript Engine - Unused memory does not get released to OS

    Votes:

    erahm, what do you think?

Currently ni, reporter hangs out in memshrink so I think we'll be able to coax some actionable data out of them.
 
  • 1312148 - Core :: DOM - Worker sending ImageBitmaps causes memory leak (memory allocated by createImageBitmap isn't collected enough?)

    Votes:

P2, patch pending.
 
  • 1313356 - Core :: DOM - nsDocument leaked with 1 unknown edge on bugzilla attachment pages

    Votes:

Defer to mccr8.
  • 1313859 - Core :: DOM - large amount of heap-unclassified related to blobs

    Votes:

    njn, froydnj, what do you think?

 P2, baku is actively working on the reporting at least.
  • 1313888 - Firefox :: Developer Tools: Console - Large memory usage after leaving the console open

    Votes:

Hold off for now, looks like a dup.
  • 1314569 - Core :: JavaScript: GC - Purge ShapeTables on compacting GC

    Votes:

P1, more jandem JS slimming.