Issue metadata
Sign in to add a comment
|
Canary 71.0.3544.2 crashing on restoring tabs after update
Reported by
amut...@gmail.com,
Sep 6
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:61.0) Gecko/20100101 Firefox/61.0 Steps to reproduce the problem: 1. Start Chrome Canary 2. Click Restore button 3. Tabs and windows come up for a couple minutes then the browser crashes What is the expected behavior? My tabs are restored What went wrong? Crashes and I get an Apple crash report with Crashed Thread: 2 Chrome_IOThread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? Yes prior version Chrome version: 71.0.3544.2 Channel: canary OS Version: OS X 10.13 Flash Version:
,
Sep 7
Attached cut/past from crash problem report app.
,
Sep 7
Unable to reproduce the issue on Mac using chrome reported version-71.0.3544.2 as per C#0 steps. It would be more helpful if you provide us latest 16 digit crash id from chrome://crashes (as attached) to triage further. Thanks..!
,
Sep 7
This morning I downloaded 71.0.3545.2 and tired again. Tab restore worked and the browser has not crashed yet. The latest crash id for Thursday September 6, 2018 at 9:06:37 AM is: d47f7d58c600ec06 Older Thursday crash id are: 6616602bf2270701, 1912b445574112b3 At this point, I am no longer blocked and I am good with you closing the issue as I no longer blocked with the current Canary version. Thank you
,
Sep 7
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
,
Sep 7
amutiso@, Thanks for the reply. As per C#4, closing this issue as Wontfix.
,
Sep 7
Err, sorry folks, I think I spoke too soon. The browser just crashed again. Crash report id: d4e422d7cfec5508 |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by meh...@chromium.org
, Sep 6