Issue is seen in Blaze and Mighty as well with today's build

Able to reproduce the issue on Blaze using chrome version 55.0.2862.3/8818.0.0

Unable to do Webrtc call using https://apprtc.appspot.com/?debug=loopback in mighty,blaze and daisy devices with 55.0.2862.3/8818.0.0 dev.

Black blank screen is seen. No video is visible

Some other Repro steps:
1) Sign in to user>> go to Camera.app>> and observe

Expected: Preview should be shown
Actual: Instead black screen is seen

2)
1. Sign in to user>> go to settings>> go to people>> click on camera>> and observe

Expected: Preview should be shown
Actual: Instead black screen is seen

Issue is seen in hangouts as well, while trying to have hangout in Daisy and Mighty devices (No video is seen)

I've asked Franky to bisect. I reproduced the black YouTube video on peach pi 8799.0.0 with tot chrome (synced today).

I could not reproduce this on elm 8799.0.0 with tot chrome (synced today).

Reverting https://codereview.chromium.org/2296433002 fixed the black video on peach pi (camera, apprtc, and youtube). I'll revert it.

https://codereview.chromium.org/2360453003 has been sent to CQ.

Issue is seen today's beta M53: 54.0.2840.33/8743.35.0 (Official Build) beta-channel  Blaze, Mighty and Daisy as well

How did that CL cause this breakage? "feature_flags_.chromium_image_ycbcr_420v = true;" ?

No idea. But "feature_flags_.chromium_image_ycbcr_420v = true;" only affects ARM. But #0 said Peppy (Intel) had the issue. I left the office and could not try reverting only chromium_image_ycbcr_420v.

Issue is not reproducible in Peppy device, have added it by mistake, but issue is still able to reproducible in Daisy, Blaze and Mighty devices with both the versions which are there in comment #0 and #11 

https://codereview.chromium.org/2360453003 was merged. I'm checking if the offending CL was in M54.

Confirmed the offending CL was merged to M54. https://codereview.chromium.org/2347453002

I verified the revert fixed veyron minnie on M55 tot. 8809.0.0 on veyron minnie didn't have the issue and 8810.0.0 had the issue. The offending CL was picked up by 8810.0.0. I'm requesting a merge of https://codereview.chromium.org/2360453003 for M54.

Daniele. Can you merge the revert to M54 after it's approved? Thanks. I'm not sure if the revert has any dependency in M54.

It sounds like this bug is ARM specific based on the devices it is showing up in?

@#20, I'll take care of it, there isn't any dependency. I also have a fix that I'm going to land ASAP on ToT. Is merging the fix to 54 a possibility?

@#21, correct it's arm specific.
We were claiming that ycbcr_420v is supported on arm devices, and sometimes that's not the case.
SW decoded video streams in chromium would try to use that format and would fail. I have a fix already for that already.

+josafat for R54 merge.

Since this is already in the release, we should probably not block new dev pushes on it.

approved

@#22 Let's do revert for now and once fix is confirmed in ToT then you can request for merge again

Reverted here: https://codereview.chromium.org/2360323004

Issue 649136 has been merged into this issue.

This issue has been approved for a merge. Please merge the fix to any appropriate branches as soon as possible!

If all merges have been completed, please remove any remaining Merge-Approved labels from this issue.

Thanks for your time! To disable nags, add the Disable-Nags label.

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

Is there any pending merge on this one ?

@josafat, not that I know. It has been reverted on ToT and 54 (https://codereview.chromium.org/2360323004)

I relanded the code, that should work now, on ToT but not in 54.

Verified on M55 build 8872.0.0