Avast causing Aw Snap
Reported by
nsiniste...@bondacom.com,
Dec 11
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3578.80 Safari/537.36 Steps to reproduce the problem: 1. Install Avast 2. Open Chrome 3. Go to anywhere (Like google.com) What is the expected behavior? Chrome should open the page What went wrong? Aw Snap! Window appears. Crashed report ID: How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? N/A Chrome version: 71.0.3578.80 Channel: stable OS Version: 10 Flash Version: We are receiving a lot of complains about it in the Help Forums. Users say that uninstall avast fixed the problem. I know that probably that's not a Chrome problem itself, but for final users that's a Chrome crash, and not an avast crash. Some users report that reinstall solve the problem for a moment, but after some time is start crashing again. We can't collect a crash report from chrome://crash, but this page is crashing too.
,
Dec 11
Hi @jbanavatu Users can't access to chrome://crashes because this carsh too. One user reports that this happen just with in Windows 10 64bits running Chrome 71 32bit version, makes any sense? You can get some info in the forum thread (There are some users discussing that): English: https://productforums.google.com/d/msg/chrome/29mbfbsPyq0/2C_sQ1zQDgAJ Spanish: https://productforums.google.com/d/msg/chrome-es/A4olzdM5gf4/0LIQL_MyBgAJ Another way to get crash reports?
,
Dec 11
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
,
Dec 11
Hi there! Good news! One user have shared with us some crash reports after remove Avast: d0bdf263-e204-4e04-9760-458063eb9e83 5b1ecace-a799-4752-9e3f-eeb4116017b8 aa81611d-d5b5-4a50-a325-199034de73f5 74223825-a7cb-4b58-9c06-b3a8d0f96e74 64d39336-9c22-44f0-905d-23fe86522adf d9f48f54-48fe-4fbf-bbb1-6c3b9090fd18 769b5591-71b4-4d00-9f7b-9fa13807aa34 2d5b86ea-a8c7-4148-aa7d-1f8b42b8baa8 b5891353-4385-4f0f-ae61-d7e669171cc3 cdb458be-ad86-4b26-a01a-c76269ceee90 6c78d35a-62a9-4653-bc9d-b78a4e6c8a2f 53e1c4e9-221c-468a-8aa1-89e5f0bddfaf Hope this helps!
,
Dec 11
,
Dec 11
Usually the reported crash IDs are not in a GUID form. They look like this: Uploaded Crash Report ID 2e414db204e34fe6 (Local Crash ID: Chrome) Would it be possible to upload the crashes and share the uploaded crash IDs?
,
Dec 11
Related to bug - https://bugs.chromium.org/p/chromium/issues/detail?id=913719#c18.
,
Dec 11
Here's a thread on the Avast forum that mentions this behavior: https://forum.avast.com/index.php?topic=223803.0
,
Dec 11
Hi there! Users reports that the last avast update fix the problem. Just as feedback, maybe in this cases a more explained screen would be really appreciated, understand which software is causing chrome crash (in this screen) can add more feedback. Of course, if you can make chrome survive to this things, that would be really appreciated! About this particular issue (Avast vs Chrome), I think that this can be marked as "Fixed" right now. Thanks!
,
Dec 11
,
Dec 11
Hey all, Since it seems the third-party anti-virus provider has issued an update that resolves this, I'm going to go ahead and mark this as WontFix. For anyone still seeing the behavior, please update your anti-virus and try restarting your computer. I'll let other folks update bug 913719 when they reach a conclusion point. Thanks! |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by jbanavatu@chromium.org
, Dec 11Labels: Needs-Feedback