[Bug 57620] New: High CPU load when setting "Screen resolution" to other value then 96
https://bugs.winehq.org/show_bug.cgi?id=57620 Bug ID: 57620 Summary: High CPU load when setting "Screen resolution" to other value then 96 Product: Wine Version: 10.0-rc3 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: winex11.drv Assignee: wine-bugs(a)winehq.org Reporter: ulrich.gemkow(a)ikr.uni-stuttgart.de Distribution: --- I am seeing a high CPU load (more than 40%) for the application and the Xorg server (also more than 40%) when setting the screen resolution with winecfg to (i.e) 192. Also the window manager shows a high load. With screen resolution 96 the high load does not happen. The application is Framemaker 8 and the Desktop Environment is somewhat special (Trinity desktop, a KDE 3.5 derivate) A bisect shows the following commit 0f1d999bb878ea54214057d3662c116271ec4812 is the first bad commit commit 0f1d999bb878ea54214057d3662c116271ec4812 Author: Rémi Bernon <rbernon(a)codeweavers.com> Date: Tue Nov 19 13:28:39 2024 +0100 winex11: Update the Win32 window state outside of event handlers. I am grateful for any advice on what further information can help to solve this problem. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57620 Ulrich Gemkow <ulrich.gemkow(a)ikr.uni-stuttgart.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Regression SHA1| |0f1d999bb878ea54214057d3662 | |c116271ec4812 Keywords| |regression -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57620 Rémi Bernon <rbernon(a)codeweavers.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rbernon(a)codeweavers.com --- Comment #1 from Rémi Bernon <rbernon(a)codeweavers.com> --- This is not entirely unexpected, as we are now doing DPI scaling on our side on the CPU, and in a probably not very optimized way. It should be improved in the future but that will require some non-trivial work that's not fit for code freeze. In the meantime, you can force individual (or all) applications to be HIDPI aware, using the documented Windows compatibility flags in the registry, see https://ss64.com/nt/syntax-compatibility.html and https://bugs.winehq.org/show_bug.cgi?id=57175#c33 (Wine extends the setting to allow setting it for every application). -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57620 --- Comment #2 from Ulrich Gemkow <ulrich.gemkow(a)ikr.uni-stuttgart.de> --- Thanks! Unfortunately the app is very old and not HIDPI aware. Setting the value in the registry as described in the bug report you mentioned makes the app unusable. The "high CPU load" problem makes setting the graphics resolution for such programs in wine 10.0 unusable. And "high load" means "eating" the whole (rather powerful) CPU - the cooler goes to max speed. In the past (before the HIDPI changes, i.e. in Win 9) setting the graphics resolutions to a higher value worked and gave benefits also for old apps. So my question is - is there a possiblity to revert to the old behavior at least until the new implementation is complete? Maybe I misunderstand things completely - then sorry! ... And thanks for your great work in wine! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57620 --- Comment #3 from Ulrich Gemkow <ulrich.gemkow(a)ikr.uni-stuttgart.de> --- "Win 9" should be "Wine 9", sorry :-) -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57620 --- Comment #4 from Rémi Bernon <rbernon(a)codeweavers.com> --- That setting should restore the old Wine behavior for HIDPI-unaware applications, by forcing them to be HIDPI aware. This is what we were doing before, so if it doesn't work, something else got broken in the way. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57620 Ulrich Gemkow <ulrich.gemkow(a)ikr.uni-stuttgart.de> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution|--- |INVALID --- Comment #5 from Ulrich Gemkow <ulrich.gemkow(a)ikr.uni-stuttgart.de> --- Setting the registry entry works. Sorry - I had to learn that after changing registry values the wineserver must terminate before further tests. Sorry about this. So the high load problem is solvable in this way and I mark this bug report as INVALID. Sorry about the noise and - once again - thank you! -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
https://bugs.winehq.org/show_bug.cgi?id=57620 Austin English <austinenglish(a)gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #6 from Austin English <austinenglish(a)gmail.com> --- Closing. -- Do not reply to this email, post in Bugzilla using the above URL to reply. You are receiving this mail because: You are watching all bug changes.
participants (1)
-
WineHQ Bugzilla