WebRTCStatsReportCallbackResolver causing tab crashes
Reported by
r...@xenleads.com,
May 3 2017
|
||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.29 Safari/537.36 Steps to reproduce the problem: 1. Create WebRTC Call 2. End Call 3. Start Another Call What is the expected behavior? New Call should establish What went wrong? It seems like occasionally on a subsequent WebRTC call it will cause the tab to close with a "aww snap" error message. We think it could be related to this commit: https://chromium.googlesource.com/chromium/src.git/+/b39b8d6fb03d46dff5556e7a5c428ac9302f5579 Here is the line that is causing the issue: hrome_child.dll!blink::`anonymous namespace'::WebRTCStatsReportCallbackResolver::~WebRTCStatsReportCallbackResolver() Line 395 Crashed report ID: 0fd4c7b6-2425-460e-978e-52be29e42030 How much crashed? Just one tab Is it a problem with a plugin? No Did this work before? N/A Chrome version: 59.0.3071.29 Channel: stable OS Version: 10 Flash Version: n/a
,
May 4 2017
Seen issue on: Windows 7 or 8 or 10, Chrome 58+ The crashing has only started since updating to Chrome 58.
,
May 4 2017
,
May 5 2017
@rob: Thanks for filing the issue. Could you please provide a sample URL to create WebRTC call. That would help us in further triaging of the issue. Thanks,
,
May 5 2017
,
May 5 2017
How are you making the first and the second calls? Are you re-loading the page or using some UI etc?
,
May 5 2017
@sandeepkumars .. We are using Plivo to make those calls (www.plivo.com), so we are not creating the actual webRtc calls. Let me see if I can share our testing URL. @hbos .. We are using angular, so there is no page refresh between calls. To give you a little more insight, this crash is not predictable. We have ~35 agents making calls, and we see this crash in about 0.5% - 1% of these calls. We have only experienced this crash on Windows (Chrome OS / Mac OSX seem to be unaffected. Thus it is going to be very hard for us to replicate this scenario. However, we should be able to get you more crash samples if needed, as we are seeing this on a daily basis since v58.
,
May 5 2017
Thank you for providing more feedback. Adding requester "sandeepkumars@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
,
May 6 2017
,
May 9 2017
We were able to replicate this issue using a virtual machine with a very low memory size (500mb). It looks like this issue is caused by the garbage collector.. you can see us replicate the issue here: https://www.youtube.com/watch?v=40NjhqggvnQ&feature=youtu.be I have attached another example in this comment. I have also asked one of my engineers to comment on this thread with some of his debugging findings.
,
May 11 2017
Can we get an update on this ticket? Is this being actively looked at?
,
May 15 2017
Chrome version 59, channel stable? 59 has not reached stable yet? Was that canary or a custom build? I'm looking through crashes and I can see this stack trace for M58 but there are no reports in M59. Looking at the crash reports I see this in versions before https://codereview.chromium.org/2772283002 landed. I'm starting to suspect this is a dup of https://crbug.com/700068 which was fixed by that CL. rob are you able to reproduce this on latest Chrome Canary? |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by r...@xenleads.com
, May 4 2017