https://bugs.winehq.org/show_bug.cgi?id=51420
--- Comment #38 from Sveinar Søpler cybermax@dexter.no --- (In reply to Kurt Kartaltepe from comment #36)
If you want to see if you are affected, well the first step is to see if you have a DVI device. The second step is you could run the same queries wine does and watch if your X11 session becomes unusable. For example `for x in $(seq 1 100); do xrandr --q1; done`, testing with a single DVI device shows the system crippled and testing with a single DP devices shows no significant impact.
So, is this supposed to happen on "any" device using DVI when doing this xrandr query? Would xorg crawl to a halt on AMD or Intel if you use `for x in
$(seq 1 100); do xrandr --q1; done`?
If such a spammy function would never ever happen on any linux program other than wine, i can see it not being fixed by upstream driver tho, and finding a better solution in wine is needed (as you point out)... however, if only nVidia GPU's would exhibit this kind of behaviour if this particular for sequence is used, perhaps it is a driver issue someone should consider bugreporting?
It does seem as the proposed fix forces 32bpp, and bypass some sort of detection (that seemingly does not work to well on nVidia with DVI + multiple displays).
I don't have a DVI port on my RTX card, so i cant really do any testing i guess.