New issue
Advanced search Search tips

Issue 649514 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 0
Type: Bug



Sign in to add a comment

tricky-tot-chrome-pfq-informational failing with FATAL: out of memory. size=0

Project Member Reported by steve...@chromium.org, Sep 22 2016

Issue description

Starting here:

https://uberchromegw.corp.google.com/i/chromeos.chrome/builders/tricky-tot-chrome-pfq-informational/builds/2096

Many (all?) VMTests are failing with:

FATAL:memory.cc(22)] Out of memory. size=0

in the chrome log.



 
There are no obvious culprits in the chrome change log, but several potential ones.

I am going to see if I can reproduce this locally, although I haven't built tricky before so it will take a while.

Cc: ihf@chromium.org
This is no longer happening.
FWIW, I was able to reproduce it locally but it is fixed in ToT.
Presumably this was a bug that affected other builders and was identified and fixed or reverted.
There were two build failures after the last failure with this symptom, so there is a long range of possible changes that may have caused this.

I may try to do a bisect anyway if I have time just to know what caused this.

Project Member

Comment 4 by sheriffbot@chromium.org, Oct 7 2016

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Project Member

Comment 5 by sheriffbot@chromium.org, Oct 21 2016

Pri-0 bugs are critical regressions or serious emergencies, and this bug has not been updated in three days. Could you please provide an update, or adjust the priority to a more appropriate level if applicable?

If a fix is in active development, please set the status to Started.

Thanks for your time! To disable nags, add the Disable-Nags label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Untriaged)

Sign in to add a comment