From:  Eric Rahm <erahm@mozilla.com>
Date:  14 Jan 2016 03:31:25 Hong Kong Time
Newsgroup:  news.mozilla.org/mozilla.dev.memory
Subject:  

Re: MemShrink Pre-Triage (11th Jan 2016)

NNTP-Posting-Host:  63.245.214.181



On Tue, Jan 12, 2016 at 7:20 PM, Nicholas Nethercote <n.nethercote@gmail.com> wrote:
On Mon, Jan 11, 2016 at 6:46 PM, Eric Rahm <erahm@mozilla.com> wrote:
>
> 975193 - Firefox :: General - Firefox takes always no more than about 1 CPU
> until it is to slow to work, even if there is more CPU available.

I don't think this should be a MemShrink bug. And it should probably
just be dup'd to the main e10s bug.


Agreed, we can just clear it.
 

> 1227275 - Firefox :: General - 70-80% e10s sessionrestore regression on
> fx-team (v.45) on Nov 20, 2015 from push 924d421d766a

Not sure why this is a MemShrink bug. No memory data that I can see.


Yeah I'm not sure how I got that impression, we can just clear it.
 

> 1235552 - Testing :: General - Automated crash burn test system

Probably not a MemShrink bug; covered by existing test suites/systems.


Sadly the proposed features probably are not covered by existing systems (playing videos, webgl, etc are not covered). But yes in theory existing systems could be adapted.
 

I'll save comments on other bugs for the meeting tomorrow!

Nick