Continuously get the Aw Snap message daily.
Reported by
ambe...@gmail.com,
Aug 9 2017
|
|||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36 Steps to reproduce the problem: 1. Tabs randomly crash, haven't been able to determine cause. What is the expected behavior? That the tabs don't crash What went wrong? There haven't been details I've been able to see in the dmp files that specify what the problem is. Crashed report ID: 1203e4be-c61e-48a4-a991-73678f1378fd How much crashed? Just one tab Is it a problem with a plugin? N/A Did this work before? No Chrome version: 60.0.3112.90 Channel: stable OS Version: 10.0 Flash Version: It doesn't seem to happen to one site in particular. It has happened in tabs using various websites. I have enabled and disabled extensions in attempts to fix it. I have uninstalled chrome and reinstalled chrome. I have also tried installing the chrome repair which also didn't seem to help.
,
Aug 10 2017
I attached all the crash .dmp files and the file name is the crash id.
,
Aug 10 2017
I also copy and pasted the most recent crash id above.
,
Aug 10 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 16 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 21 2017
ambeb24@ - Please provide the crash report id(16) as shown in the comment #5, not the local crash id as per the comment #6. This will help us in triaging the issue further. Thanks...!!
,
Aug 21 2017
Thank you for providing more feedback. Adding requester "krajshree@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 5 2017
Is there an update on this? It seems to be getting worse. Crashing more frequently. This morning my chrome browser refused to launch a site I need for work and this is becoming a big problem for job performance.
,
Sep 5 2017
To clarify a bit, see the "Send now" link at the buttom of the screenshot? That sends the minidump file to our servers for analysis, and then gives a different number, a non-local one, where we can look it up. The servers handling the report do a bunch of decoding and analysis on it.
,
Sep 5 2017
I clicked send now on every crash message I had in chrome://crashes please update me as soon as you can about this issue.
,
Sep 5 2017
Thanks for doing that. That should update the list you see in chrome://crashes with a new, shorter crash ID, saying "Uploaded Crash ID" rather than the previous "Local Crash ID" (sometimes take a few minutes or so, though). When that happens please provide a few of these numbers here.
,
Sep 5 2017
(Restricting view due to minidumps attached --- probably don't want those publicly viewable).
,
Sep 6 2017
Come to think of it, I may have accidentally made this inaccessible to the reporter; if so I apologize. Deleting the attachments rather than restricting; seems like a better approach.
,
Sep 18 2017
Is there an update on this? It is still occurring and impeding my ability to work.
,
Sep 18 2017
Please provide the new crash #s you should see for things that you uploaded in chrome://crashes now.
,
Nov 3 2017
ambeb24@ Can you please reply to comment #18, which will help us to investigate this issue further. Thanks..
,
Feb 11 2018
Closing due to lack of feedback requested but not provided. If the issue still exists please open a new issue be sure to quote the chrome://crashes server ids |
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by hdodda@chromium.org
, Aug 10 2017Labels: Needs-Feedback