When Chrome has a whole-browser crash, it no longer tells you "Whoa! Google Chrome has crashed. Relaunch now?"
Reported by
93m4qau...@gmail.com,
Jan 28 2018
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36 Steps to reproduce the problem: 1. Open about:inducebrowsercrashforrealz. 2. Let Chrome give out on you in the following seconds. 3. Wait for a popup to come up explaining what just happened. What is the expected behavior? In the past years, there would be a popup that would come up when Chrome crashed that read "Whoa! Google Chrome has crashed. Relaunch now?" What went wrong? When Chrome just suddenly crumbles under your feet, it doesn't let you know anymore what just happened. There could be a popup that reads "Oops! Chrome just slipped up and had to crash. Relaunch now? [Yes][No]" Did this work before? Yes Not sure Chrome version: 64.0.3282.119 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Attached is a screenshot of Chrome from a few years back when it slipped up on me.
,
Jan 28 2018
,
Jan 29 2018
Tested the issue on Win-7 and Win-10 using chrome reported version #64.0.3282.119 and latest canary #66.0.3334.0. Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Opened about:inducebrowsercrashforrealz. 2. The browser crashed immediately. 3. On reopening the browser, a restore pop up appeared to restore all the tabs. Note: Same behaviour is observed in M-60 and M-50 chrome builds also. reporter@ - Could you please let us know when was the last time approximately, the popup appeared when Chrome crashed that read "Whoa! Google Chrome has crashed. Relaunch now?". This will help us in triaging the issue further. Thanks...!!
,
Jan 29 2018
,
Feb 22 2018
A few years back is all I really know. I probably wouldn't call it a regression as it's so long ago now.
,
Feb 22 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Feb 23 2018
As the issue is not reproducible in latest chrome builds. Hence, removing the Needs-Bisect label. Thanks...!!
,
Mar 6 2018
As per comment #7, adding TE-NeedsTriageHelp and requesting someone from UI>Browser team to look into this issue and help in further triaigng. Thanks..
,
Mar 22 2018
It seems that this bug is being caused by https://cs.chromium.org/chromium/src/chrome/app/google_chrome_strings.grd?l=349, which specifies that Windows be excluded.
,
Mar 22 2018
This bug is reproducible in the latest Chrome builds - the "Whoa! Google Chrome has crashed. Relaunch now?" dialog isn't being shown as it is expected to.
,
Mar 22 2018
Actually, after analyzing the code a bit more, I think that the code specifies that Windows be the only platform. Correct me either way.
,
Nov 23
*** Mass UI Triage *** We were unable to reproduce this bug. If this bug still reproduces for you, please reopen or file a new issue. Thanks! |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by krajshree@chromium.org
, Jan 28 2018