"Aw Snap" tab crashes when video is playing back in a non-focused tab.
Reported by
chad.del...@mlb.com,
Mar 6 2018
|
|||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36
Steps to reproduce the problem:
The use case is multiple tabs with video playing back in each tab. The video in the non-focused tab will cause an "Aw Snap" to show at some point during playback.
What is the expected behavior?
What went wrong?
"Aw Snap" error clears browser tab.
Crashed report ID: 1b4c318b4e0d3525 (Local Crash ID: 60bfa2d0-1385-4b88-9ade-d3b24a094c0e)
How much crashed? Just one tab
Is it a problem with a plugin? No
Did this work before? N/A
Chrome version: 64.0.3282.186 Channel: stable
OS Version: OS X 10.12.6
Flash Version:
Additional crash dumps below:
- Uploaded Crash Report ID 5a171361b8140fe9 (Local Crash ID: 9150555a-2dab-40c1-8c93-e7dbac86b2d5)
- Crash report captured on Monday, February 26, 2018 at 5:26:40 PM, uploaded on Monday, February 26, 2018 at 5:26:41 PM
- Uploaded Crash Report ID 9b62141c27ece2cd (Local Crash ID: 52941ac5-afa9-447c-a6b1-2b161c07becb)
- Crash report captured on Sunday, February 25, 2018 at 4:37:12 PM, uploaded on Sunday, February 25, 2018 at 4:37:13 PM
- Uploaded Crash Report ID 9b6dcf556be15dfc (Local Crash ID: 6c81ebc3-9cd7-4889-961d-676d50c16a7d)
- Crash report captured on Sunday, February 25, 2018 at 3:57:11 PM, uploaded on Thursday, March 1, 2018 at 9:48:28 AM
- Uploaded Crash Report ID eedf4598a7dc89b9 (Local Crash ID: 2bcfc173-bc77-48ed-b563-0d0843072185)
- Crash report captured on Sunday, February 25, 2018 at 3:48:53 PM, uploaded on Thursday, March 1, 2018 at 9:48:28 AM
- Uploaded Crash Report ID 39a3321b7b8d08be (Local Crash ID: d35e903c-358d-4387-b361-6e4c16d21afe)
- Crash report captured on Sunday, February 25, 2018 at 3:43:54 PM, uploaded on Thursday, March 1, 2018 at 9:48:28 AM
- Uploaded Crash Report ID 4fe68b762a00da5b (Local Crash ID: d3bd19ed-8ba4-4557-a6cf-2ee0ced44c0f)
- Crash report captured on Sunday, February 25, 2018 at 3:43:39 PM, uploaded on Thursday, March 1, 2018 at 9:48:28 AM
- Uploaded Crash Report ID 172f00ea97b388db (Local Crash ID: b74c10a7-6c3a-4f5b-87c3-8e86e186168f)
- Crash report captured on Sunday, February 25, 2018 at 3:32:04 PM, uploaded on Thursday, March 1, 2018 at 9:48:28 AM
- Uploaded Crash Report ID c31adbd78b1e7268 (Local Crash ID: 6be876bc-c244-45f5-9519-651f72b99ea9)
- Crash report captured on Sunday, February 25, 2018 at 3:15:54 PM, uploaded on Sunday, February 25, 2018 at 3:21:05 PM
- Uploaded Crash Report ID dd5cda4a3f5cb851 (Local Crash ID: 6624192c-5536-4f2f-bebf-e928f313d2a1)
- Crash report captured on Sunday, February 25, 2018 at 2:37:40 PM, uploaded on Sunday, February 25, 2018 at 2:54:38 PM
- Uploaded Crash Report ID 0248a0ac27acdb21 (Local Crash ID: f2e12cf9-8dbb-4dcc-ae40-e9f9466a4a1b)
- Crash report captured on Sunday, February 25, 2018 at 2:00:16 PM, uploaded on Sunday, February 25, 2018 at 2:00:16 PM
,
Mar 6 2018
This bug showed up in my inbox this morning, and I'm not sure where to route it. Matt, Caleb, can either of you help these folks understand what is going on in the crash report and direct them further? If you can find any evidence for what JS behavior triggers the crash, I've volunteered to help determine a workaround at that layer that might help them avoid the crash until it is fixed in Chrome.
,
Mar 6 2018
From inspecting the first couple crash reports, this looks like it is probably a duplicate of bug 815058. +yukishiino@ to continue triage.
,
Mar 6 2018
Thanks for responding. Let me know if you need any additional info.
,
Mar 7 2018
As per comment #3 duping this into Issue 815058, hence merging into it. Please undo it, if it not the case.
,
Mar 7 2018
We just experienced another crash. This time on Canary ( Version 67.0.3364.0 (Official Build) canary (64-bit) ). Was the issue (815058) suppose to be fixed in Chrome 66 or greater? Crash report below. f02f45fea0be284a (Local Crash ID: e6e9b2d7-2393-4791-9d06-937b967b5ff3)
,
Mar 7 2018
Additional Canary crash reports below: 3b30cdf1e0c1e7bb (Local Crash ID: aff0d405-871c-4d6d-8d03-78134c29b0f8) ed232e15a2dc0525 (Local Crash ID: f95819a8-abf8-4d1a-8f50-9aee452d715c)
,
Mar 8 2018
Additional crash report below: 4158f8bf610e9f83 (Local Crash ID: 7a1c3ec2-c6d0-412e-971d-64f8e17cd228) |
|||
►
Sign in to add a comment |
|||
Comment 1 by joeyparrish@chromium.org
, Mar 6 2018