GPU acceleration doesn't work (Windows 11, AMD FirePro W2100)

[burtonsys]

It appears that Min is currently maintained, in that there've been two releases in the last month, but I installed it on Windows 11, and when I run it I just get a white screen. It does appear to be trying to do something, as a couple of cores are pegged at 100%. Alt-F4 exits it, but nothing else does anything. (This is on a big desktop workstation computer with lots of cores and lots of RAM.)

The latest version mentioned in the release notes on the website is 1.33.1, the "product version" embedded in the installer is 1.33.1, and the embedded "product version" and "file version" in min.exe are both 1.33.1.0.

[PalmerAL]

It should work, although someone else reported something similar also recently (#2497). Can you try editing the desktop shortcut to add the --disable-gpu flag and then relaunch?

[burtonsys]

Thank you, PalmerAL! Adding the --disable-gpu option solved the problem.

The white screen problem and the two threads stuck at 100% CPU usage are both solved. Here's a pair of Process Explorer screenshots:

Broken:
https://sealevel.info/min-browser_white_screen_bug1.png
("3.57%" means one CPU core / hardware thread is pinned at 100% usage.)

Not broken:
https://sealevel.info/min-browser_working_properly1.png

For reference, my main display adapter (driving the first two monitors) is an AMD FirePro W2100, and I also have an old Nvidia GeForce 310 installed for the 3rd monitor.

By odd coincidence I have a "new to me" (used) AMD RX480 GPU that I just bought yesterday, but I haven't installed it yet.

[Meloman42]

Can you disable this default GPU acceleration in future releases and add an option in the settings? min browser performs best on older PCs, but even the "--disable-gpu" option makes it somewhat difficult to use.

[PalmerAL]

Disabling it reduces performance a lot, so I don't think we should do that by default. Having a settings option would be a good idea though.

An even better way would be to have it disabled on initial startup, then once startup is successful, enable it for all future sessions. I'm not sure if we can detect that reliably though.