https://bugs.winehq.org/show_bug.cgi?id=51420
--- Comment #35 from matt gardotd426@gmail.com --- (In reply to Sveinar Søpler from comment #34)
Can't say i have ever experienced this, but i do not use a DVI monitor. Mine is DP on main, and HDMI on my second monitor.
Maybe it is some strange stuff with multi-monitors with one of them connected to DVI? I get around 1.3-2% 1-core load when running regedit.
RTX2070. Currently 470.62.13 driver, but did not have this with 495.44 either.
If you wonder where that strange "falling back to randr 1.0" message comes from: https://github.com/wine-mirror/wine/commit/ f5e6c086f91749e9e302c1abf858807535bc9775
Some of this is removed with the proton fshack patchset: https://github.com/ValveSoftware/wine/commit/ 352b0304a357f9e062695c45ed12d74e0cfc70db
Not sure if it is related to this bug, but you mentioned the message.. and it is logged in wine logs and (should) not in Xorg.0.log. Perhaps try WINEDEBUG=-all,+xrandr ?
Normal log: 0070:trace:xrandr:X11DRV_XRandR_Init Found XRandR 1.6.
Yeah as I said my theory is that it affects users with 2 monitors where one of them is connected via DVI. The fact that you don't experience the bug seems to bolster that theory a little bit more.
My patch posted here has been confirmed to fix the issue (at least for one of the users here who were affected), so while waiting for a true fix, anyone affected can use my patch if they're building from source (or using something like wine-tkg-git to build for them).