https://bugs.winehq.org/show_bug.cgi?id=51420
--- Comment #54 from mitchell4136@gmail.com --- (In reply to haphazardsasquatch from comment #53)
So I thought I'd test this, too. debian 11, nvidia 418.211.00 from non-free, winehq-devel 7.0~rc5~bullseye-1 and winehq-devel 6.11
The current version starts causing 99.5+ cpu usage in htop as soon as anything wine starts running (winecfg for example), 6.11 is clean.
I couldn't find a difference in connecting an external dvi display, even without one - just using the laptop's internal one - this bug occurs.
Given that we know the offending commit, matt has written a first patch and we have multiple independent reproductions, is there anything else a user can supply to help, so that this regression doesn't make it into the upcoming stable release?
thanks
I think it was figured out that it's not exclusive to DIV-D displays, but rather displays that at the hardware level only support a single resolution (still potentially in multi-monitor configs), and require GPU scaling for lower resolutions. These kinds of monitors tend to like DVI-D as input but i saw another bug report that was marked a duplicate of this one that was on a laptop hooked up to an HDMI display.