New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 772598 link

Starred by 2 users
Status: Duplicate
Merged: issue 772191
Owner:
wfh@chromium.org
Closed: Dec 2017
Cc:
█ krajshree@chromium.org
█ ramyan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Got STATUS_TIMEOUT exit code opening profile - and sad tab

Project Member Reported by wfh@chromium.org, Oct 7 2017 
Chrome Version: 63.0.3234.0 (Official Build) canary (64-bit) (cohort: 64-Bit)
OS: Win10

What steps will reproduce the problem?
(1) Open new profile and quickly hit Ctrl-T for new tab
(2)
(3)

What is the expected result?

No crash

What happens instead?

Sad tab. No crash report, but chrome://histograms shows one entry:

Histogram: CrashExitCodes.Renderer recorded 1 samples (flags = 0x41)
258  ------------------------------------------------------------------------O (1 = 100.0%)

This is 0x102 which is STATUS_TIMEOUT. I'm not sure why a renderer would return this exit code. It warrants investigation.

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

Comment 1 by fi...@chromium.org, Oct 9 2017

Owner: treib@chromium.org
Status: Assigned (was: Untriaged)
To figure out the right priority for this bug: How quickly do you have to hit Ctrl+T - is it a real world problem or more like an artificial crash?

Comment 2 by treib@chromium.org, Oct 10 2017 

Could this be  bug 772191 ? Can you try if it still reproduces after r507339?

Comment 3 by manoranj...@chromium.org, Oct 10 2017

Labels: Needs-Bisect Needs-Triage-M63

Comment 4 by krajshree@chromium.org, Oct 11 2017

Cc: krajshree@chromium.org
Labels: Needs-Feedback
Unable to reproduce the issue on Win-10 using chrome reported version #63.0.3234.0 and latest canary #63.0.3236.0.

Attached a screen cast for reference.

Following are the steps followed to reproduce the issue.
------------
1. Opened a new profile and quickly hit Ctrl-T for new tab
2. Observed that new tab opened without any issues and did not observe any sad tab.

wfh@ - Could you please respond to comment #2 and please let us know if the issue reproduces after r507339?

Thanks...!!
772598.webm
2.4 MB View Download

Comment 5 by fi...@chromium.org, Oct 23 2017 

gentle ping @wfh

Comment 6 by mastiz@chromium.org, Nov 7 2017

Owner: wfh@chromium.org
Reassigning to wfh@ to follow up on the questions above, thanks!

Comment 7 by wfh@chromium.org, Nov 14 2017 

Yup I only managed to repro once and not reliably, but I was seeing spikes in Uma for this error code. Have these dropped now?

Comment 8 by mastiz@chromium.org, Dec 12 2017

Mergedinto: 772191
Status: Duplicate (was: Assigned)
Closing this bug as dup since we can't repro and UMA timeline shows the spike for WAIT_TIMEOUT was transient starting on the 2017-10-04 and spiking on the 2017-10-12: https://uma.googleplex.com/p/chrome/timeline_v2/?sid=dda8d473b56df92029aa5405dc981620
►

Sign in to add a comment