New issue
Advanced search Search tips

Issue 593141 link

Starred by 1 user
Status: Duplicate
Merged: issue 592040
Owner:
wfh@chromium.org
Closed: Mar 2016
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

renderer failed launch count increase on canary

Project Member Reported by rkaplow@chromium.org, Mar 8 2016 

OS: windows

On march 5 we saw a massive increase in renderer failed launch.The crashes were all on 51.0.2667.0 and 51.0.2667.1 - no other versions.

Comment 1 by wfh@chromium.org, Mar 8 2016

Mergedinto: 592040
Status: Duplicate (was: Assigned)
same root cause as 592040 because chrome.exe had been deleted from underneath the running chrome, new tabs were unable to start. This should correspond to a spike in child process launch error codes of that particular type.

Comment 2 by wfh@chromium.org, Mar 8 2016 

I don't see a jump in any of the CrashExitCodes.Renderer codes between 4th/5th/6th March UMA data. This might be indicative of a bug.

Comment 3 by wfh@chromium.org, Mar 8 2016 

also the fact that this has continued worries me. perhaps we have a set of users still running the broken version.
►

Sign in to add a comment