Thanks for your report! I am not able to repro this issue on Tab 3 / 4.4.2 on 58.0.3029.83 I am able to play vimeo video with out any lag or corruption. Can you please provide bug report for further investigation?

To attach bugreport:

Android Settings > About Phone > Tap Build number 10 times, go back one screen, Developer options should be right above About phone.
Check the USB debugging then Take the bug report

Attached is the bug report 

Deleted: bugreport.txt 12.8 MB

bugreport.txt 12.8 MB View Download

Thank you for providing more feedback. Adding requester "rsgavara@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

We don't have this device, so can't repro. rsgavara@ is yours a model SM-T310?

Do you still see this issue if you install Chrome Canary on the device?

Do other apps like YouTube, etc work?

I haven't tried Canary. I used Chrome beta and the same thing happened. Youtube app works fine. Rolling back to stock Chrome on the device fixed the green/pink static but audio was way out of sync. 

Just tried Canary with projectalpha.com and Vimeo and it's doing the same thing. 

Thanks; just to be sure, have you tried rebooting the device during this time? The KitKat era MediaCodec APIs are not particularly stable.

Doing a restart now but I did restart after noticing the issue the first time. 

Still getting the issue after a restart. Tried in Canary. 

Tried the same sites on my Google pixel using chrome stable and the videos work fine. I also updated the latest canary on the affected tablet and the videos are still showing the green and pink static.

@rsgavara can you answer the Q in c#6? This information will help us decide if we need to blacklist this device.

I understand. I'm trying to determine if it's just your device that's having problems or the entire range of SM-T310 models. If it's all of them, we'll have to blacklist MediaCodec usage.

(This will still fall back to MediaPlayer so video playback will work).

Sorry I deleted the comment after I saw it was not intended for me.

Mine is Galaxy Tab 3 (7 inch) (SM-T210R) and Galaxy Tab 3 (7 inch) SM-T211) and I couldnt repro this issue.

Thanks. alexcruz7787: If you go into chrome://flags and flip "disable accelerated video decode." Are you able to play videos on the device anymore?

My accelerated setting was disabled so I enabled it. Vimeo could play but
it was very choppy and slow but project alpha would not play; it only gave
me the play button but didn't do anything.

Oh interesting, if you already have disabled hardware playback. I'm not sure what else we can do. Chrome isn't playing the videos in that case, we're sending them to Android MediaPlayer.

rsgavara@ can you flip chrome flags "disable accelerated video decode" on your SM-T211 and see if you get the same playback issues? +tguilbert in case it's an issue with our MediaPlayer stack.

Ah, I think I misread, disable in your case means hardware decode was enabled, you flipped it to disable hardware decode and this ends up using MediaPlayer which is what I expected. I'm surprised even that's not performing decently though.

I dont see any issue after disabling "accelerated video decode" flag from chrome://flags.

Okay, thanks. Unfortunately there's not much more we can do to help alexcruz. Flipping the disable hardware decode flag is as good as it's going to get given the factory installed version is lagging too. Unfortunately video playback on these early devices is not very good and has lots of bugs.

Do any other browsers provide a good video experience on the device?

I tried Firefox and the video wasn't even supported. The weird thing is
removing the latest Chrome update on the tablet and reverting back to stock
plays the video.

YouTube provides a fallback for older versions of Chrome which is why that playback is working. Unfortunately we aren't able to get them to provide that fallback for newer versions, so this is WontFix. I recommend upgrading your device if you are able as there are many security issues with old devices like these that even the latest version of Chrome won't be able to help you with. Sorry and good luck!

Thanks for the help everyone.