https://bugs.winehq.org/show_bug.cgi?id=56725
Bug ID: 56725 Summary: chromium not working under new wow64 Product: Wine Version: 9.8 Hardware: x86-64 OS: Linux Status: NEW Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: dark.shadow4@web.de Distribution: ---
Downloader: https://commondatastorage.googleapis.com/chromium-browser-snapshots/index.ht...
Make sure not to use too new chromium because of bug 56724
https://bugs.winehq.org/show_bug.cgi?id=56725
Fabian Maurer dark.shadow4@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- URL| |https://commondatastorage.g | |oogleapis.com/chromium-brow | |ser-snapshots/index.html?pr | |efix=Win/1255378/ Keywords| |download
https://bugs.winehq.org/show_bug.cgi?id=56725
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |wow64
https://bugs.winehq.org/show_bug.cgi?id=56725
Ken Sharp imwellcushtymelike@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |source
https://bugs.winehq.org/show_bug.cgi?id=56725
--- Comment #1 from testator@protonmail.ch --- Created attachment 76581 --> https://bugs.winehq.org/attachment.cgi?id=76581 chromium-127
There's alot of peices to the puzzle of getting latest chromium working on WoW64. You're going to need PR's from gitlab: 3747, 5044, 5440, 5496?, 5512?, 5752?, and the userfaultfd patch from the writecopy bug? Most of those pr's need rebases. PR 5666 recently got merged which was neccessary for this as well. Suffice it to say that chrome's sandbox does not work so that causes bugs without 3747? And multi process webview shared rendering doesn't work without 5666? 5044 is needed for threadraces in ntdll. The userfaultfd patch is presuambly needed for chrome's usage of writecopy in sandbox although if I remember right wine devs keep getting some strange hack upstreamed into chrome to make it work anyways in wine.
The picture was taken using the above PR's and wine-staging's patchset, without the writecopy hack, on new WoW64 without dxvk and no special command line options which works for me. Played a game of slither.io with it just fine and opened up a few webpages. CEF still doesn't work though which is what i've been trying to get working. All these points are seperate bugs some of which have reports and some of which don't. Maybe make a report on the threadraces and sandboxing/DeriveCapabilitySidsFromName so those get merged/fixed?
https://bugs.winehq.org/show_bug.cgi?id=56725
testator@protonmail.ch changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |testator@protonmail.ch
--- Comment #2 from testator@protonmail.ch --- Ignore my inane ramblings, the version you linked does not work even with my stupid setup.
https://bugs.winehq.org/show_bug.cgi?id=56725
--- Comment #3 from testator@protonmail.ch --- Created attachment 76582 --> https://bugs.winehq.org/attachment.cgi?id=76582 chromium-123-single-process
Specifically you have to pass --single-process and then it loads the browser and just works with my WoW64 setup with the linked chromium 123 version. Haven't figured out why multi process chromium isn't working yet even with shared rendering. Launching with --in-process-gpu makes the screen render for a moment then it blacks out without crash but no response. Probably a duplicate of bug #44985
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.
-
WineHQ Bugzilla