Regularly getting aw snap error on page
Reported by
step...@upside.com,
Sep 22 2017
|
|||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.113 Safari/537.36 Steps to reproduce the problem: 1. Launch https://alley.chat/ 2. Leave tab open for a while 30 minutes or so 3. Come back to aw-snap What is the expected behavior? Chrome doesn't crash What went wrong? Chrome aw snaps for me multiple times a day on chrome mac os x. 60.0.3112.113 (Official Build) (64-bit) Did this work before? N/A Chrome version: 60.0.3112.113 Channel: n/a OS Version: OS X 10.12.6 Flash Version: Site is establishing like 9 websocket connections and using webrtc to do peer to peer communication. Im not exactly sure whats breaking chrome.
,
Sep 22 2017
,
Sep 23 2017
A crash id associated with this crash Crash ID: crash/c39df3f57ffa0a30 hope that helps!
,
Sep 25 2017
Unable to reproduce the issue in MacBook Pro (Retina, 15-inch, Mid 2014), 10.12.6 using chrome stable version #61.0.3163.100 and latest canary #63.0.3223.0. Following are the steps followed to reproduce the issue. ------------ 1. Launched https://alley.chat/ 2. Left tab open for more than 30 minutes. 3. Did not observe any aw snap crash. stephen@ - Could you please check the issue on latest canary #63.0.3223.0 by creating a new profile without any apps and extensions and please let us know if the issue still persist or not. Thanks...!!
,
Sep 25 2017
This app seems to constantly leak memory when it is opened. Looking at the heap profile a large portion is coming from the system/Native context sending over to the webrtc team to determine if there is a memory leak.
,
Sep 26 2017
It doesn't look like there are canary builds available for linux. But I went ahead and ran 61 with extensions disabled and was able to reproduce the crash. Crash ID: crash/d3a6773634114f90
,
Jan 22 2018
Mac triage: duplicate. The linked crashes are being tracked as issue 542522 already.
,
Jan 22 2018
Will this bug get updated if the secret bug I can't see gets fixed? |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by step...@upside.com
, Sep 22 2017