https://feedback.corp.google.com/product/208/neutron?lView=rd&lIssueType=all&lRSort=1&lROrder=2&lRFilter=1&lReport=84973689473 

Looks like this is on a Kefka (Braswell).

Does this happen on other systems also?

Can we bisect to where this first started failing?

The issue can reproduce on all devices. VUDU used Flash in the past but now it change to new player that may cause the issue.

Joseph@, so the last time we tested VUDU it was using Flash?

Vsuley@, Yes it was using Flash

We need to promote to beta soon, is there any chance we can get this fixed in the next couple days?

Is possible someone to contact Vudu? because they did some change on their site which no longer use Flash

+folks whom may know how to find an account manager for Vudu (even though this is a site not an Android app)...

If this is a change on their side, then I don't think we should necessarily block beta on it. 

Does the failure also repro on the existing beta/stable?

yes issue can reproduce on both beta and stable

Thanks, in that case there is not much point in blocking.

Is there any reason we need to keep this bug private?

If we can open it up we can direct Vudu people to it.

I was not able to find any video stack-related errors in the report. There was one audio error:

audio_sync_reader.cc(177)] ASR: No room in socket buffer.: Broken pipe (32)

However I'm not sure if this was related, or might've been a result of the failure rather than a cause.

Can we get clarification on why this was filed as restrict view Google? If we are to engage with Vudu we need to open the bug up for them to see it.

posciak@, any update on this issue?

Not sure if posciak@ can help here. Assigning to bhthompson@ to decide if we should assign to a developer engagement team or to follow some other route. 

We emailed the alias just CCed, I think we need help from Vudu to do much here.

recharging this bug - could it be that vudu made a change to REQUIRE output protection? working with Adobe Primetime team, they indicated that in general any content that requires output protection (vs. best-effort/requesting) will fail immediately.

which makes me wonder if primetime output protection required has EVER worked on chromeOS.

ericde@, Joseph also mentioned that this repro'd for him when trying to use Win10 + Chrome but could not repro when using Win10 + Edge. Have we ruled this out as being at the browser level? 

issue no reproduce on M-69 build 10895.40.0, 69.0.3497.73 and M-70 build 11005.1.0, 70.0.3532.8, close it!