Issue metadata
Sign in to add a comment
|
Hangup signal does not cause Restore Tabs dialog on next start
Reported by
jidanni@gmail.com,
Sep 25
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.92 Safari/537.36 Steps to reproduce the problem: 1. $ chromium siteA siteB siteC & 2. $ killall -1 chromium 3. chromium What is the expected behavior? There should be a popup: "Chromium did not close properly last time. Restore tabs?" What went wrong? No such popup. Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? Yes Chrome version: 69.0.3497.92 Channel: n/a OS Version: Flash Version: Here we gave chromium SIGHUP. Please also test with other signals.
,
Sep 25
Note yes in Settings, user has: On startup Open the New Tab page set. But that shouldn't affect the Restore Tabs dialogue.
,
Sep 26
@ jidanni: Could you please provide 16 digit crash id from crashes and also provide screen-cast of the issue which helps in better triaging. Thanks!
,
Oct 5
As I mentioned in other bugs, those crash IDs aren't available on Debian Linux "sid". (Not your Google version. The public version.) All you need to do is simply run my above test. P.S., I never said it crashed. (But yes, crash is the best bug category.)
,
Oct 5
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 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by jidanni@gmail.com
, Sep 25