Google Canary Crashes 30 - 40 times in last 48 hours
Reported by
bustyasi...@gmail.com,
Feb 8 2017
|
|||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3002.0 Safari/537.36 Steps to reproduce the problem: Hi, Google Canary has crashed 30 - 40 times in the last 48 hours. What is the expected behavior? I never seen Google Canary crash this many times ever!!! What went wrong? Hi, Google Canary has crashed 30 - 40 times in the last 48 hours, even when I am not loading a web page and leaving the browser alone it still crashes? Crashed report ID: n/a How much crashed? Whole browser Is it a problem with a plugin? N/A Did this work before? N/A Chrome version: 58.0.3002.0 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: I would like to add some comments for the Chrome Team to look into. 1. I am sorry I can't send you the crash report, I have tried many times in Google Canary. 2. Is it possible to make the browser automatically send you the crash report when a user clicks on the "restore" button. 3. I have tried sending a crash report through my browser and the system information BUT when I have restarted Google Canary I feel the correct system information is not getting send to you and so I am writing this to suggest creating an automatically send crash report,...
,
Feb 9 2017
@bustyasianescorts2 -- Thank You for the report. Checked for the issue on Latest Canary# 58.0.3006.0, surfed for more than one hour and did not observe any Crashes. Could you please upgrade your Canary to latest available version and let us know whether you are still facing the Crashes. If Yes, navigate to chrome://crashes if possible and provide us the latest generated Crash ID which would help us to triage the issue more further. If you are not even able to navigate to chrome://crashes, please let us know. Thanks in Advance.
,
Feb 11 2017
Hi, It has not crashed for another 48 hours now. But I have some crash reports to give you so hopefully will help you out: Crash ID e56dd2db-1ec6-43b5-b3d8-617c2abee096 Crash ID 16fd0b30-82c3-4d92-84af-9852a6ebaa91 Crash ID 12f2c308-16b3-4172-8bcf-0f8f224f37cd Crash ID 2326fc34-e177-423e-b5ce-39cb6a7c3782 Crash ID 52c4d319-a357-4cf6-b6f7-e43270f6a952 Crash ID 1664d90a-df70-4af0-a3bc-608c1ff9eee2 Crash ID b3e0e94e-dd03-432d-af1d-cc9a1e497a9a Crash ID 84e60f92-ff3e-4bcd-a18c-01b6ab3101fb I think that should be enough, thanks for the chrome://crashes I will bookmark that and any future problems will use that.
,
Feb 13 2017
Marking this as won't fix as this issue no longer occurs. Please feel free to raise a new issue , if you face any issues in latest chrome channels along with the server id , which is next to the crash id in chrome ://crashes . Thanks! |
|||
►
Sign in to add a comment |
|||
Comment 1 by nyerramilli@chromium.org
, Feb 9 2017