Regularly seeing the "Aw Snap!" error in Chrome (Mac).
Reported by
yyefet@chromium.org,
Jul 22 2016
|
||||
Issue descriptionVersion: 51.0.2704.79 (64-bit) OS: Mac One specific enterprise user is experiencing 'aw snap' crashes on Chrome (Mac) when accessing certain sites. The issue is not reproducible with other users on the same machine. Troubleshooting steps: - cleared cookies & cache - updated Chrome to latest version - Current version is 51.0.2704.79 (64-bit) - incognito mode - The same issue occurs - removed extensions - Issue still occurs - reset browser settings to default - Issue still occurs - removed user profile from the Mac and created new - Issue still occurs - re-imaged Mac - Issue still occurrs - sign into a completely different Mac - Issue still occurs - uninstalled Chrome and reinstalled - Issue still occurs - ran chrome w/ --safe-plugins flag - Issue still occurs. What steps will reproduce the problem? (1) User logs into Chrome browser on Mac (2) Navigates to one of the URL's below (3) Aw Snap crash Examples of URL's visited when this issue occurred: https://www.linkedin.com/recruiter/profile/41621295,jzap,CAP?searchController=searchV2&searchId=3820485863&pos=4&total=52&searchCacheKey=44e35a16-82c6-4e8a-8a3a-c864321720c6%2CL7Ok&sl=NPS_R%3B44e35a16-82c6-4e8a-8a3a-c864321720c6%2CL7Ok%3B4%3B44e35a16-82c6-4e8a-8a3a-c864321720c6%2CL7Ok&memberAuth=41621295%2Cjzap%2CCAP https://www.google.com/url?q=https%3A%2F%2Fwww.linkedin.com%2Frecruiter%2Fprofile%2F41621295%2Cjzap%2CCAP%3FsearchController%3DsearchV2%26searchId%3D3820485863%26pos%3D4%26total%3D52%26searchCacheKey%3D44e35a16-82c6-4e8a-8a3a-c864321720c6%252CL7Ok%26sl%3DNPS_R%253B44e35a16-82c6-4e8a-8a3a-c864321720c6%252CL7Ok%253B4%253B44e35a16-82c6-4e8a-8a3a-c864321720c6%252CL7Ok%26memberAuth%3D41621295%252Cjzap%252CCAP&sa=D&sntz=1&usg=AFQjCNGbO7vUfq6tElptsH_UYu0RunCq2w https://www.google.com/url?q=https%3A%2F%2Fwww.linkedin.com%2Frecruiter%2Fsearch%3FsearchHistoryId%3D3819186143%26searchCacheKey%3D24ef157a-7408-46b4-afde-618ae90ba189%252Ck5SA%26linkContext%3DController%253ApeopleSearch%252CAction%253AresultsWithFacets%252CID%253A3819186143%26page%3D1%26start%3D0%26count%3D25&sa=D&sntz=1&usg=AFQjCNFah9KSGcDHbjlJp6xfqyqjrJHoHg *Crash ID's: 7cefd6d600000000 34446e3600000000 9f42400200000000 chrome://profiler output: (PII protected) https://drive.google.com/a/google.com/folderview?id=0B6fESMmJITTNazR6TDNoTFhLd1k&usp=sharing What is the expected output? Able to navigate to site What do you see instead? Aw snap crash
,
Jul 22 2016
The three stack traces point to Out of memory
,
Jul 25 2016
[mac triage] There are 33,687 crash reports for users of this Extension - https://chrome.google.com/webstore/detail/onelogin-for-google-chrom/ioalpmibngobedobkmbhgmadaphocjdn Does uninstalling it from chrome://extensions stop the regular crashes? 8/10 crashes sharing a client ID have that extension loaded. One of the two that doesn't shows a subdomain of onelogin.com . So I suspect it's some buggy javascript either in the extension or a site that's trying to rely on it. (I don't see anything at the chrome://profiler output link, but `Take Heap Snapshot` under `Profile` in DevTools may provide further insight).
,
Jul 25 2016
tapted@, the customer removed the onelogin extension and encountered 'aw snap' crash after doing so. Crash ID post 'onelogin' extension removal: 9f42400200000000 They also attempted to remove 'OfficeDocEditing' extension and received a crash after that as well. Crash ID post 'OfficeDocEditing' extension removal: 34446e3600000000
,
Jul 26 2016
> One of the two that doesn't shows a subdomain of onelogin.com This is still the case for http://go/crash/9f42400200000000 The other is bullhornstaffing.com, which also shows up in the previous list of crashes. So signs still point to the particular sites the client is visiting having buggy javascript that is consuming all the available memory. > `Take Heap Snapshot` under `Profile` in DevTools may provide further insight
,
Aug 1 2016
tapted, The customer provided a heap snapshot. I uploaded the file to the share below (PII protected): https://drive.google.com/a/google.com/folderview?id=0B6fESMmJITTNazR6TDNoTFhLd1k&usp=sharing
,
Aug 3 2016
Unfortunately, that's a heap snapshot of linkedin.com - I don't think that's the cause. linkedin.com may still crash if it's been bundled into the same process as the buggy site due to memory constraints. It's probably bullhornstaffing.com or the subomain of onelogin.com that has the buggy javascript. The crashes all have an uptime of ~7 hours, so the site is probably leaking memory slowly over time, then crashing multiple tabs when the memory runs out. Sorry, I understand this is frustrating, but it's unlikely there's anything we can do on the Chrome side to fix this. So I'm closing this bug. Please ask the client to reach out to the website owners of bullhornstaffing.com or the subdomain of onelogin.com. to help the website owner diagnose the problem. I suggest the webmaster open a single URL for one of the pages that crash (no other tabs), leave Chrome running for a couple of hours, then take a heap snapshot to isolate their buggy code. |
||||
►
Sign in to add a comment |
||||
Comment 1 by meh...@chromium.org
, Jul 22 2016