Tested on Android Version 5.0.2, no issues

Tested on 6.0.0, no issue

Tested on another Samsung Galaxy s7 running 6.0.1, same result as reported

CORRECTION: Wrong Chrome and Webview Version 

version: 50.0.2661.89 is CORRECT

Test on One Plus Two running 6.0.1 and chrome 50.0.2661.89. Phone not affected 

This seems like a Samsung specific issue, likely a driver bug.
TE can you please repro this on device suggested in #1. 

I Agree, I have tested on other Samsung devices and LG devices and One Plus Devices running the same version numbers and different versions. 

Only the Samsung S7s seem to be affected.

It looks like there is an issue between the Chrome JS engine and the OS, Firefox which i think is using a different JS engine doesn't have this issue. I would guess it isn't the Chrome JS engine that is the problem as other devices running the same versions are OK. However this is the extent of my debugging ability. I am going to attempt later to debug the JS running on the webpage to see if i can find the code that actually causes the crash, but whether i get anywhere, who knows.  

Is this the right place to report this bug, or do i need to report it somewhere else. 
 

This is unlikely to be related to JS - it's almost certainly a graphics driver bug. This is the right place to report it; if we can reproduce it we can follow up with the graphics hardware vendor and see if it's possible to work around the bug.

I have Tried rolling back my chrome version and have the same affect. 

I have been able to reproduce the bug on:

2 x Samsung Galaxy S7 edge (UK)
1 x Samasung Galaxy S7 (UK)

Have you been able to reproduce this bug yet? 

I don't think we were able to repro this. I see your phones are UK model, I wonder if there is anything different with models in US?

I'm experiencing the same issue on my UK Galaxy S7. So far just on one page, looks like the crash occurs when I scroll to a video ad. 

Can you share what this page is? Is it easy to repro. I think someone in our london team can try.

Also anyone that can reproduce this attach a bugreport after the reboot?

sounds like chrome, not webview

I had issues with: http://www.fieryflavors.com/spicy-food-hiccups . Page (apparently) loads successfully but scrolling causes a restart. And I still had hiccups. 

I have the issue on this page as well, don't need to scroll down just wait 15 to 20 seconds and phone powers off. 

It appears to be when something on the page is loaded, both sites appear to attempt to launch some sort of advertising video so I'm assuming this is the trigger. 

If you are right and it is issues with the Samsung display driver it looks like there are a few issues with it. 

If my phone is on standby and the screen is face down, when you get a text the edge screen is supposed to give you a notification I belive. But I just get two big Blue bars down each side of the screen. Is this th3 same for you goober? 

Google guys do I need to report this as a separate bug ? 

How do you get the bug report bo? 

> How do you get the bug report bo? 

These instructions seem correct: https://sites.google.com/site/barksideapps/tips-and-tricks/take-bug-report-on-android

> Google guys do I need to report this as a separate bug ? 

That doesn't sound like a chrome bug. File it against samsung

sounds related to video? chrome m50 has spitzer now, so it could be hardware decoder, not rendering?

UK vs non-UK: the S7 has an exynos chipset, except for the US and china.  i've seen a similar issue with an exynos chipset, so it might be related.  In that case, the page has a bunch of videos, but maybe that was a red herring.

spitzer or not, m50 will use HW decoding if possible, just via MediaPlayer for src=.  If it's a HW bug, we might find it either way :)

So after loads of messing around trying to enable USB debugging which Samsung Knox Disables, I have finally managed to generate a bug report. I am just rerunning the crash to ensure you have as much info as possible, but where would you like me to send it or should i upload here?

Ok so attempting to reproduce the bug, it looks like the sun.co.uk have just released a new version of their webpage, and i dont get a crash there anymore. 

However i do get a crash at http://www.fieryflavors.com/spicy-food-hiccups 

actually, i misread the other bug.  symptoms are similar, but it was a QC-based device.  still, the chipset difference might explain why it doesn't repro.

Ok so i have a bug report, where should i sent it ?

> Ok so i have a bug report, where should i sent it ?

zip it and attach it to this bug

Ok i have attached the bug report, I think what you are looking for is around line 113,000 only reference to fatal error i could find, hope this helps.

Deleted: bugreport.zip 3.1 MB

bugreport.zip 3.1 MB Download

Update: new chrome version doesn't not affect this bug, versions shown below. 


Chrone Version: 51.0.2704.81
Webview version: 50.0.2661.86

Have you been able to reproduce yet ? 

International version of s7 edge. Kernel panic says this:
kernel BUG at drivers/media/platform/exynos/mfc/s5p_mfc.c:155!

According to wikipedia
"""
Multi Format Codec, an intellectual property core present within the Samsung Exynos SoCs to offer hardware accelerated encoding and decoding of video formats such as MPEG-2, MPEG-4, H.263, H.264, VC-1 and VP8.
"""

So really is hardware decoding.

Media folks, anyone want to take a look here. Disable hardware decode?

See #30

Has any progress been made with this ? 

tested this on Samsung Galaxy s7 Edge /Android version: 6.0.1 and chrome 52.0.2743.32 beta not able repro , lloydbruce93 @ could you please re- check and update. Thanks

the repro page not even has media on it. this is not media related. give to blink team. Please feel free to re-assign to any appropriate owner team.

Looping in respective TE's for TE-Verification on Android.

Sorry missed this one. Looks like it doesn't repro with Spitzer enabled, so it seems our demuxing or codec usage differs enough to be safe.

Doesn't seem to repro anymore based on comments, so closing.

Happening in s6 edge. Started a month back.