Hi,
There are a number of other GPU flags that you can try which are listed at that command line website you found.
But before you go down that rabbit hole.. first check with Sysinternals Process Explorer that the "--disable-gpu" flag was actually passed to the external webview2 process. A screenshot of how it should look like is in the AdditionalBrowserArguments documentation.
Another thing to try is to see if you can confirm that the same problem happens with the WebView2 component itself.
There's a compiled version available from a link on this page: MS WebView .net example.
On top of all that you might also consider enabling logging and see if the log has something interesting to note about this issue, see AntView logging functionality.
Hope this helps tracking down the issue.
--
Wil
There are a number of other GPU flags that you can try which are listed at that command line website you found.
But before you go down that rabbit hole.. first check with Sysinternals Process Explorer that the "--disable-gpu" flag was actually passed to the external webview2 process. A screenshot of how it should look like is in the AdditionalBrowserArguments documentation.
Another thing to try is to see if you can confirm that the same problem happens with the WebView2 component itself.
There's a compiled version available from a link on this page: MS WebView .net example.
On top of all that you might also consider enabling logging and see if the log has something interesting to note about this issue, see AntView logging functionality.
Hope this helps tracking down the issue.
--
Wil