chrome://flags,
hardware-accelerated video decode, disable it

We are running these devices in kiosk mode and they are managed remotely through Chrome Device Management. 

If we login as guest on the devices, the flags settings don't stay and we haven't found a way to set the flags through the device management console.

I do see a policy named HardwareAccelerationModeEnabled

https://chromium.googlesource.com/chromium/src.git/+/afa408f66929b4a7742506f9482d0aaa8ece84e4/components/policy/resources/policy_templates.json

you want this policy made available in cpanel?

Is cpanel what we access via admin.google.com (Device Management Console)?

If so, then yes please.

Is there another way we could push it out to the devices?

maxkirsh@ Are we able to add this policy to admin panel?

Any update on this? We are having severe issues at some of our clients with this problem and really need to push this policy out.

kprimke@ would you know how to route this feature request?

tl;dr: enable HardwareAccelerationModeEnabled [1] to the
admin console (?), effectively surfacing the user flag
chrome://flags/#disable-webrtc-hw-decoding

[1] https://chromium.googlesource.com/chromium/src.git/+/HEAD/components/policy/resources/policy_templates.json#10025

I opened for server team http://b/122258087 and pointed to a doc for requesting a new policy in Admin Console.

Hi, I didn't get the exact reproduce step. Could you elaborate?
What device is used here?

We're using an Aopen Chromebox mini using Google Device Management and enterprise enrollment for all devices.

We run a multi-frame, browser-based signage solution that also pulls Youtube videos. We find (particularly, but not exclusively in cases where the resolution is 720p), that the visual side of the browser crashes after a few days running the signage. The rotation of the frames continues in the background as the sounds of the videos keep playing in correct sequence - it seems to be just the GPU that has crashed.

How was the reproduce rate? Do we need to run the app for a few days?

Yes. Definitely have to run it for a few days. Some devices reproduce it and some don't.

Attached is a log of a device that experienced the crash at around 1:59 on January 6, 2019.

Deleted: logs_20190106-2251.zip 1.1 MB

logs_20190106-2251.zip 1.1 MB Download

Here's a video of what the test channel looks like frozen. As you can see the screen has frozen, but the audio continues to rotate in the background (the beeping signifies the end of the test countdown video).

Deleted: 20190107_112403.mp4 12.9 MB

	20190107_112403.mp4 12.9 MB View Download

I have no "Aopen Chromebox mini" in my hand.
Since johnylin@ has it, assign to him.
I set this P3.  jseliger@, is the priority ok?

Thanks hiroh@.

This is causing us substantial issues in the field, so the highest possible priority would be appreciated.

Also, right now the priority should be providing an option to disable hardware acceleration in Chrome Device Management. Hopefully this will help us avoid the symptoms of the issue (albeit not addressing the root cause).

Any update?

johny hasn't tested this. Let me try to reproduce with some BayTrail devices on my hand. Could you give me the introduction how to run kiosk app? 

Sure. App ID is imoeidgonlnmjbnecfopbendmgglkoid. It's hosted on the Google Chrome Developer Dashboard.

Once it's installed, please send me the unique ID on the blue page and we can get it hooked up for you. 

Do you have a 720p monitor? We found that to be one of the risk factors.

Can we set manual policies or have hardware acceleration set as a device management option in the meantime?

It turns out my office doesn't have Baytrail device.
Johny, could you look into this with your ninja?

Thanks.


Can we set manual policies or have hardware acceleration set as a device management option in the meantime?