From:  Nicholas Nethercote <n.nethercote@gmail.com>
Date:  13 Jan 2016 11:20:51 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 Mon, Jan 11, 2016 at 6:46 PM, Eric Rahm  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.


> 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.


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

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


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

Nick