This bug was spun off from 812529 because it is a separate issue.

Comment thread:

Comment 25 by vasanthakumar@chromium.org, Feb 27
Delete comment ⚐
@Shenghao: The camera we used is a 4K Camera. This issue could be reproducible for all 4K cameras. 

Feel free to try with other models with 4K (if possible). 
Comment 26 by bhthompson@google.com, Mar 7 (5 days ago)
Delete comment ⚐
This bug is marked as blocking 65 stable, which is going to try to promote next week, any chance we can get a fix this week?
Comment 27 by shenghao@chromium.org, Mar 9 (4 days ago)
Delete comment ⚐
Cc: shenghao@chromium.org
Owner: junov@chromium.org
I tested the exact webcam (Logitech BRIO 4K) on cyan with 10323.30.0. The bug is not reproducible, while on panther it is reproducible.

I think it has to do with the chrome media stack changes between 65.0.3325.65 / 10323.30.0 and 64.0.3282.144 / 10176.68.0. Chrome camera app is the same, but the former reproduces the bug while the latter doesn't.

junov@,
Could you take a look or assign to proper person?


Comment 28 by bhthompson@google.com, Yesterday (27 hours ago)
Delete comment ⚐
Labels: -Pri-2 Pri-0
This needs to be fixed today, or we need to reclassify it as non blocking.

Upping priority to reflect the release schedule.
Comment 29 by tovep@chromium.org, Today (3 hours ago)
Delete comment ⚐
Labels: -Pri-0 -ReleaseBlock-Stable ReleaseBlock-StableCFM Pri-1
I don't think we should block the general ChromeOS rollout on this, but we should really see what we can do about this issue before rolling out to CfMs.

Junov, are you working on this?
Comment 30 by tovep@chromium.org, Today (3 hours ago)
Delete comment ⚐
Labels: Hotrod-Platform-Tracking Proj-Hotrod
Comment 31 by tovep@chromium.org, Today (3 hours ago)
Delete comment ⚐
Labels: ReleaseBlock-Stable
I think I'm adding back the ReleaseBlock-Stable.

I believe that it is blocking a stable release on CfMs, but we can keep the CfMs pinned to 64 until it is resolved even if a ChromeOS stable release is done today with this problem.

However, I can't judge if this is a blocker for ChromeOS in general.  Who can make that judgement call?

(Please leave the ReleaseBlock-StableCFM label even if the ReleaseBlock-Stable label is removed.)
Comment 32 by tovep@chromium.org, Today (3 hours ago)
Delete comment ⚐
Labels: -Pri-1 Pri-0
Comment 33 by bhthompson@google.com, Today (2 hours ago)
Delete comment ⚐
We should certainly try to fix this, but using an external 4k USB camera is a somewhat obscure use case for the bulk of the fleet, the majority of the Chrome OS devices out there have built in camera.

If we get a fix we would merge it, but if it comes down to it we may punt the bug, we still have some time, if we can get a fix today or early tomorrow we can still make the first stable RC (last nights build has other blockers in it we need to clear). 
Comment 34 by tovep@chromium.org, Today (108 minutes ago)
Delete comment ⚐
From what I read above it seems reproducible on M65 but not M64.

Who can bisect and find the breaking change?