HI .. Been battling with a problem recently, and I just found the 'workaround'.
HPE Server systems come with an OOB management web page called iLO.
The latest iLO 5 has a problem with the latest renderer that Chromium has implemented (SWANGLE), this causes the CPU of your machine to ramp up to 100% when displaying the console of a server (making it useless).
However, a workaround is to launch Chrome with the '--use-gl=swiftshader-webgl' option, to revert it back to the original renderer.
Is there a way with RDM Chrome web sessions, to enable this option ?
Even if it's to launch 'external' as the tabbed would probably not work that well anyways.
Let me know.
Very interesting find. We actually have a to-do to change the iLO session to support Embedded Edge. Most of the code is already done but we have no way of testing other than an old iLO 2 here in house. I would be interesting to see if you have the same issue with Embedded Edge. We could finish the integration "blindly", set it as experimental and maybe you could give it a try. What do you think?
As for the --use-gl=swiftshader-webgl option we would need to investigate if it is possible for us to set it.
Stéfane Lavergne
I'll have a look using embedded Edge, but I am guessing it's the new Chromium variant; so possibly suffers from the same thing.
HPE will eventually figure a workaround, but it'll be a firmware update to the iLO code.
Since you're launching the browser embedded or external, could you not put an advanced option to add switches to the executable ?
Rather than create a checkbox or something similar, which would only really be good for one use case.
I believe we we can pass switches when we start the Chrome executable so in theory we should be able to fix this.
I've logged an enhancement to add the option to send --use-gl=swiftshader-webgl when we start the Chrome embedded session. We will let you know when it's available so that you can give it a try.
P.S.: Sorry for the delay, I must have missed your reply from 3+ weeks ago.
Stéfane Lavergne
Hello,
The new version of RDM is now available, could you update your RDM to the latest version and see if your issue still occurs?
Please note that a database upgrade may be required depending on the version of RDM that you are currently using.
For more information on that matter, please consult this link:
https://docs.devolutions.net/rdm/windows/installation/database-upgrade/
Best regards,
Patrick Ouimet