New issue
Advanced search Search tips

Issue 747653 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Certain websites flash and crash chrome

Reported by nick.cip...@gmail.com, Jul 22 2017

Issue description

Example URL:
apkmirror.com

Steps to reproduce the problem:
1. Visit an affected site.

What is the expected behavior?
The website loads correctly and doesn't crash chrome.

What went wrong?
Chrome crashes and doesn't load the page.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? N/A 

Did this work before? Yes Not sure

Does this work in other browsers? Yes

Chrome version: 61.0.3163.0  Channel: canary
OS Version: 8.0.0
Flash Version: 

Here is a video of what happens: https://photos.app.goo.gl/RLH3gEcXgntZyYTI2

Another website that displays this behavior is hivehome.com

I've tried uninstalling and reinstalling Chrome Canary as well as clearing it's data.

The issue has been happening for over a month and every time it makes Chrome crash I send a report in saying that Chrome crashed while trying to load apkmirror.com and it happens with other sites as well, but I guess that section of feedback isn't checked?
 
Enable the "Always Use Flash/H.248" options and then download "VLC" from the Play Store. On many occasions, this may help with viewing content.
Is that suggested as a permanent solution or as a temporary fix until it's fixed in Chrome? I don't think that would be a very good option for every Android Chrome user to have to do if the issue makes it's way into public release, so I'm assuming it's just a temporary fix?
@vssummer I looked in the flags menu and couldn't find anything called "Always Use Flash/H.248".

I did try downloading VLC and it didn't help Chrome load the web page, it still crashes.

Comment 4 by kojii@chromium.org, Jul 24 2017

Cc: kojii@chromium.org
Labels: Needs-Feedback
NextAction: 2017-08-06
I can't reproduce the crashes on the reported sites, tested on Nexus 6p.

Could you mind to go to "chrome://crashes" and tell us the crash report ID if there were one listed there?

Comment 5 Deleted

Comment 6 Deleted

My comments appear to be getting auto-deleted. Am I doing something wrong?

Comment 8 Deleted

Comment 9 Deleted

Comment 10 Deleted

Project Member

Comment 11 by sheriffbot@chromium.org, Jul 24 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "kojii@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
Sure kojii, these were all from the issue and everything listed in that menu. Hope it helps!

b7af585688000000 (Local Crash ID: Chrome)
Crash report uploaded on Saturday, July 22, 2017 at 5:17:45 PM

a5fcebdaf8000000 (Local Crash ID: Chrome)
Crash report uploaded on Saturday, July 22, 2017 at 3:24:46 PM

139e4dfe40000000 (Local Crash ID: Chrome)
Crash report uploaded on Saturday, July 22, 2017 at 1:30:48 AM

254d820688000000 (Local Crash ID: Chrome)
Crash report uploaded on Friday, July 21, 2017 at 6:41:28 PM

771c79fe40000000 (Local Crash ID: Chrome)
Crash report uploaded on Friday, July 21, 2017 at 3:52:31 PM

fd6b0c2268000000 (Local Crash ID: Chrome)
Crash report uploaded on Friday, July 21, 2017 at 2:23:41 AM

Let me know if there's any other information I can provide. Thanks!
There we go, apparently it didn't like me having "Crash Report ID" before every ID? Weird.

Or maybe I hit a character limit?

Comment 14 by kojii@chromium.org, Jul 24 2017

Components: -Blink Internals>Compositing
Thank you, the first hexadecimal string is the ID, sorry for my poor explanations.

It looks like your device is failing to use GPU properly, passing over to experts. If you could tell us what your device is, that might help them too.

compositor_impl_android.cc:785 content::CompositorImpl::OnGpuChannelEstablished(scoped_refptr<gpu::GpuChannelHost>)

Sure, it's a Nexus 6P.
Happy to report that the issue appears to be fixed in DP4.

Comment 17 by kojii@chromium.org, Jul 25 2017

NextAction: ----
Owner: kojii@chromium.org
Status: WontFix (was: Unconfirmed)
Thank you for letting us know that, and that you for taking time to report this problem!

Sign in to add a comment