tab unresponsive kill does not result in crash in chrome://crashes |
||
Issue descriptionChrome Version: 56.0.2924.79 (Official Build) beta (64-bit) OS: Chrome OS 9000.76.0 (Official Build) beta-channel chell What steps will reproduce the problem? (1) visit https://www.adn.com/politics/2017/02/01/murkowski-announces-she-will-vote-against-trumps-education-secretary-nominee/ (2) wait a while, maybe 30 secs. (3) Kill/Wait hung renderer dialog appears. Click "Kill". What is the expected result? crash in chrome://crashes What happens instead? No crash shows 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.
,
Feb 1 2017
I get the same behavior with chrome://hang, with no crash report being generated, so that's probably an easier repro.
,
Feb 1 2017
I get entries in the ChildProcess.HangRendererType in the RENDERER_UNRESPONSIVE_IN_FLIGHT_EVENTS (1) bucket.
,
Feb 1 2017
I also got records in the Tabs.SadTab.KillCreated histogram for each time the sad tab was produced, so perhaps this is just related to it being a "kill" rather than a "crash"
,
Sep 7
|
||
►
Sign in to add a comment |
||
Comment 1 by wfh@chromium.org
, Feb 1 2017151 KB
151 KB View Download