https://bugs.winehq.org/show_bug.cgi?id=56725
testator@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #76582|0 |1 is obsolete| |
--- Comment #4 from testator@protonmail.ch --- Created attachment 77687 --> https://bugs.winehq.org/attachment.cgi?id=77687 chromium-123-in-process-gpu-wine-10.0_rc3
This bug is still present as of 10.0-rc3. However applying gitlab PR 7064 on top of PR's 3747, 5512, and the userfaultfd writecopy patch allows chromium-123 to render with only --in-process-gpu passed to the executable. This is a improvement over needing to pass --single-process and over --in-process-gpu causing it to render for a moment and then blackscreen and then become unresponsive. Howbeit in this state the browser gui renders and is responsive but it does not process web content which results in a infinite load of webpages, even internal to chrome like the settings page.
The picture was taken using the above PR's on new WoW64 without dxvk on vanilla wine-10.0-rc3 in a fresh prefix with corefonts installed.