iLO HTML5 console crippling performance in Microsoft Edge 93+

[aireynol]

I am seeing an issue where html5 console for ilo4 and ilo5 causes the client cpu to shoot to 100% and cause the webpage to hang. Issue is present in Edge 93 stable and newer and not present in Edge 92 and older.

I am seeing the issue within a Server 2019 vm but have also tried Win10 20H1 vm and it is also present there. Interestingly it is not present on my laptop with latest Edge. So I am thinking this may be related to GPU hardware acceleration.

Anyone seeing this issue?

[aireynol]

Edit: confirmed disabling hardware acceleration in Edge on my laptop causes the issue to appear also.

[UserName1]

We have the exact same problem but disabling hardware acceleration has made no difference.  Running Edge 95.

[aireynol]

Thanks for the confirmation.

I narrowed down the version of Edge this was introduced in:

https://docs.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel#version-93096138-september-2

It is also an issue in latest Google Chrome so this is a Chromium issue.

There is a bug here that seems very similar to this case but was closed as won't fix. There may have been some update to the webgl detection logic. So will proabably need an iLO update from HPE to fix.

https://bugs.chromium.org/p/chromium/issues/detail?id=1261406&q=gpu&can=1

[UserName1]

Ok so the long and short is Chromium nor HPE will fix this so back to using Firefox as that doesn't display the issue (at the moment).

[aireynol]

For now yes, I would hope for an updated ilo firmware from HPE though.

[aireynol · Accepted solution]

I tracked this down to a recent change in Chromium that changes the default renderer from legacy SwiftShader GL to SwANGLE. A workaround until HPE can provide an update is to use the flag --use-gl=swiftshader-webgl

Source:

https://groups[dot]google[dot]com/a/chromium.org/g/ozone-reviews/c/Q84FY6bZ4UA

(Note: for some reason the forum won't allow to post this link, hence the [dot])

[Team_Server]

Same Problem here. Start edge with --use-gl=angle --use-angle=swiftshader ist working.

[UserName1]

Also just tried it with the most recent 96 version and no luck either.

[Team_Server]

Have you tried starting edge witgh "--use-gl=angle --use-angle=swiftshader"? For me this is working.

[UserName1]

Just tried that again still maxes out the CPU to 100%

[l_lang]

The mentioned workaround doesn't work for me neither, same for Chrome and Edge. Who would have thought that you have to use IE for HTML5? What annoys me the most is that since today there is no official statement from HPE that this problem exists, or am I blind?

[G3389]

Edge and Chrome both have a function that can be controlled by Group Policy that will also rectify this issue.
Enable the below policy(s) to disable 3D graphics APIs.

Microsoft Edge
Computer Configuration\Administrative Templates\Google\Google Chrome\
Policy Name: Disable support for 3D graphics APIs
Policy Setting: Enabled

Chrome
Computer Configuration\Administrative Templates\Microsoft Edge\Google Chrome\
Policy Name: Disable support for 3D graphics APIs
Policy State: Enabled

[Team_Server]

Thanks, G3389. This works perfektly.

[WesDomon]

For anyone that doesn't have the Chrome or Edge ADMX packages imported, just use this Registry change. I didn't have a "Google" or "Chrome" key so I had to create them. Re-launched Chrome and the issue immediately disappeared.

Valid for Chrome Browser version 9 or later.

Windows registry:
Key Path: HKLM\Software\Policies\Google\Chrome\
Value Name: Disable3DAPIs
Value Type: Boolean (REG_DWORD)
Value Data: 1

[UserName1]

Thanks for the registry, that worked for chrome.  Do you know the keys for Edge?  I have tried various combinations based on the Google one in the registry with no luck.

[Team_Server]

HKCU\SOFTWARE\Policies\Microsoft\Edge\Disable3DAPIs=1 REG_DWORD

[l_lang]

Many thanks for the keys. They finally seem to work.

[UserName1]

Awesome - thanks, thats worked a treat.