Issue metadata
Sign in to add a comment
|
After the 01Nov build all pages give ‘aw smap’
Reported by
qaz...@gmail.com,
Nov 2 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (iPhone; CPU iPhone OS 11_0_3 like Mac OS X) AppleWebKit/604.1.34 (KHTML, like Gecko) CriOS/62.0.3202.70 Mobile/15A432 Safari/604.1 Steps to reproduce the problem: 1. Open chrome canary 2. 3. What is the expected behavior? No What went wrong? I updated to the November 1 build of canary. After that all tabs result in aw snap. I rebooted and reinstalled canary and that did not help. Crashed report ID: No. It will not even load that or ‘about chrome’ How much crashed? Whole browser Is it a problem with a plugin? No Did this work before? Yes Prior canary build Chrome version: Latest Channel: canary OS Version: High Sierrra Flash Version: None
,
Nov 2 2017
Unable to reproduce the issue on Mac High Sierra and Win-10 using latest canary #64.0.3255.3 Attached a screen cast for reference. Following are the steps followed to reproduce the issue. ------------ 1. Updated chrome to latest canary and observed that all the pages rendered without any issues. qazwsx@ - Could you please check the issue on by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
Nov 2 2017
When I go to people->add person I also get 'aw snap'. *every* window gives 'aw snap'
,
Nov 2 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
,
Nov 2 2017
I just re downloaded the canary installer and it has a different md5 hash the the installed from yesterday. But I have the same symptoms. here are the two md5 hashes: 8468c5b03f2d954ef4201756ec6a8b8f (Nov01) 5be29531b4d8b97c6a082aca458bde99 (Nov02)
,
Nov 2 2017
I'm seeing this behavior as well on my windows machine, running version 64.0.3256.0
,
Nov 2 2017
Guessing this is the same cause as the linked bug.
,
Nov 3 2017
The linked bug is not publicly viewable, can we get a Tl;dr? Also, this seems very similar the symptoms in this bug as well: https://bugs.chromium.org/p/chromium/issues/detail?id=779074
,
Nov 3 2017
The version I downloaded today (Nov03) with this md5 works! MD5 (googlechrome (4).dmg) = 492e13ca48dd097cd47dec66c0da3988 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by infra...@gmail.com
, Nov 2 2017