able to repro Nexus9/MOB30P/51.0.2704.81

Is this fixed if you go to chrome://flags and enable unified media pipeline?

(Can't repro with the unified media pipeline at least, M52)

Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

--enable-unified-media-pipeline fixes it for Chrome Browser.

apart from original questio which is solved I'd like to add that this affects Chromium WebView 51.0.2704.81 which in turn affects everybody that loads webview in non-debug-mode (which is way all kiosk browser apps that I have checked in the market do it) as 
adb shell 'echo "chrome --enable-unified-media-pipeline" > /data/local/tmp/webview-command-line'
will be ignored https://android.googlesource.com/platform/frameworks/webview/+/android-cts-5.1_r8/chromium/java/com/android/webview/chromium/WebViewChromiumFactoryProvider.java#117
if I understand the code right

timav@ did you fix something here w/ looping recently?

As a desperate user who has tried everything lately (including Firefox, where looping works hehe) I can see that there are some changes in latest chrome beta for android 52.0.2743.49.
"--enable-unified-media-pipeline" (unified pipeline is OFF by default) has become "--disable-unified-media-pipeline" (and unified pipline is ON by default). Thus previously one had to set the flag and looping worked, in latest beta looping does not glitch by default.

Btw I posted related ticket today https://bugs.chromium.org/p/chromium/issues/detail?id=623943
As stated above in this thread for standalone Chrome Browser there is this ability for END USER (meaning somebody that does not know what rooting, adb tools and setting flags in COMMAND_LINE_FILE path is) to set flag (now default on), but that does not apply to straight-WebView-dependant things which I am actually looking for (Android app that uses built in WebWiew cannot loop video).
So... if the latest Chrome Browser 52.0.2743.49 beta by default uses unified-media-pipeline, I hope that it will make it's way someday also in WebView (52.0.2743.49 beta does not has it).

Thank you!

Yeah sorry, that was supposed to be default on for M51 but we had some trouble, we are aiming for an M52 launch now.

No prob, thanks for your work! May I ask also there then here quickly - is it planned for unified pipline to be by default ON for final WebView R52 (as mentioned earlier - currently Chrome Browser 52.0.2743.49 beta default is ON, WebWiev 52.0.2743.49 beta default is OFF)? I'm probably crossposting now, I don't know which devs here work on what, sorry for that. Say, and I will stop :) and just bump the ticket submitted in Mobile>WebView category time to time then. Thank you!

Not for WebView unfortunately, it won't be default on until M53 for WebView due to additional complexity in WebView.

Ok, thanks. So I'll wait starting July for first WebView 53.x betas that hopefully will have this and around mid September for R53 (according to Chromium Development Calendar ;)) Thank you again!

c#6: yes, https://codereview.chromium.org/2053473002/

This issue has been moved once and is lower than Pri-1. Removing the milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

I'm unable to reproduce this issue neither on N9 with MOB30P (i.e. volantis-userdebug 6.0.1 MOB30P 2960889 dev-keys), system WebView 44.0.2403.117, nor on N9 with Android N build NRD90G.

On the other hand Spitzer was enabled for WebView in https://codereview.chromium.org/2057743002

I would mark it "fixed" if I could reproduce. Back to Dale.

Re-tested again and  unable to repro on Nexus 9 and Samsung Galaxy-SCH-I925/JZ054k