Chrome crashed
Reported by
hyli...@msn.com,
Nov 30 2016
|
|||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36 Steps to reproduce the problem: Our client's chrome crash frequently after upgrade to chrome 54.0.2840.99m. When downgrade to 49,everything is OK. We got some crash dump log. but we cannot find the crash reason. Can someone help us analyse those dump log file ,find the probable reason？ Thanks！ What is the expected behavior? What went wrong? Chrome crashed， Crashed report ID: How much crashed? Just one tab Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 54.0.2840.99m Channel: stable OS Version: Flash Version:
,
Dec 1 2016
Thanks for reply. The filename of dump file which has uploaded looks like a guid, isn't it crash id? I got a snapshoot of chrome://crashes from client's browser. But we are in China,you know,network is cut down from Chrome. So the crash infomation may not send to Chrome server.
,
Dec 2 2016
hylinwt@msn@ Chrome stable will be upgrading to 55.0.2883.75. Please upgrade to the chrome latest version and please let us know if the issue still persists. Thanks..
,
Dec 5 2016
We will test and feedback @55. But I still want to find the definite reason(maybe some specific js code trigger it?) which trigger the crash, can you give some key infomation from dump logs of crashes? Thanks.
,
Dec 8 2016
we had upgrade 55,but the issue still persists. crash id is 2a33fe58-157e-4f4b-b7ba-c70cf7a37d28 dump log also uploaded.
,
Dec 15 2016
Thank you for providing more feedback. Adding requester "sureshkumari@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 26 2016
any updates？
,
Dec 27 2016
Thanks for the update. Could you please provide the Crash ServerID generated under chrome://crashes which would help us in triage the issue further. Thanks.
,
Dec 30 2016
crash id is 2a33fe58-157e-4f4b-b7ba-c70cf7a37d28 crash report was failed to send to chrome server because we are in china. so I had uploaded the dump log file, see it in Comment 5.
,
Jan 6 2017
Thank you for providing more feedback. Adding requester "sureshkumari@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage. Ref bug 684919
,
Mar 13 2017
,
Mar 15 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||
►
Sign in to add a comment |
|||||||||||||||
Comment 1 by ajha@chromium.org
, Nov 30 2016