http://bugs.winehq.org/show_bug.cgi?id=32010
Bug #: 32010 Summary: Guild Wars 2 updater uses always 100% of a CPU core Product: Wine Version: 1.5.15 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: nob.dir.info@gmail.com Classification: Unclassified
The launcher of Guild Wars 2 (where you enter your user name and password) uses a complete core to run (even if I don't write anything or move it).
I think it's bug, because X comes laggy too, and on Windows 7 its don't uses a whole core to run.
http://bugs.winehq.org/show_bug.cgi?id=32010
nob.dir.info@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nob.dir.info@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=32010
nob.dir.info@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Component|-unknown |user32
http://bugs.winehq.org/show_bug.cgi?id=32010
Dmitry Timoshkov dmitry@baikal.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|nob.dir.info@gmail.com | Component|user32 |-unknown
http://bugs.winehq.org/show_bug.cgi?id=32010
Brandon Corujo haku08879@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |haku08879@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=32010
Jase Whipp jason.whipp@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jason.whipp@gmail.com
--- Comment #1 from Jase Whipp jason.whipp@gmail.com 2013-01-04 15:30:30 CST --- See: http://bugs.winehq.org/show_bug.cgi?id=11674
The core of this issue is a duplicate to the issue I linked above..
http://bugs.winehq.org/show_bug.cgi?id=32010
--- Comment #2 from nob.dir.info@gmail.com 2013-01-05 09:07:27 CST --- Not really. This issue is like Guild Wars 2 refreshes its window the most often possible, even when it's not needed.
https://bugs.winehq.org/show_bug.cgi?id=32010
--- Comment #3 from Austin English austinenglish@gmail.com --- Is this still an issue in current (1.7.35 or newer) wine? If so, please attach terminal output.
https://bugs.winehq.org/show_bug.cgi?id=32010
Guillaume R guillaumeraffin@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |guillaumeraffin@free.fr
--- Comment #4 from Guillaume R guillaumeraffin@free.fr --- Created attachment 51409 --> https://bugs.winehq.org/attachment.cgi?id=51409 GW2 launcher's wine log.
I confirm that this is still an issue: the GW2 launcher uses a lot of CPU. If you connect to the GW2 account it doesn't change anything. Once you're in the game everything is normal, i.e. it's just the launcher which has a problem, not the whole game.
https://bugs.winehq.org/show_bug.cgi?id=32010
Uwe Pfeifer alphatrax@t-online.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alphatrax@t-online.de
--- Comment #5 from Uwe Pfeifer alphatrax@t-online.de --- I'm having the same problem. It's still downloading but the launcher uses much CPU.
https://bugs.winehq.org/show_bug.cgi?id=32010
Xen wine@xenhideout.nl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine@xenhideout.nl
--- Comment #6 from Xen wine@xenhideout.nl --- On 64-bit prefix for me this issue also completely causes the screen to no longer be redrawn.
Until you launch the game by going ahead anyway (the cursor does change).
On 32-bit the system becomes slow but not unusable.
This has been true (at least the 64-bit thing) for every version I have tried, including 1.7.35, 1.7.4, and 1.9.5-staging.
With 1.9.5-staging and 32-bit prefix and 32-bit program, the application performs at its best for me for now.
https://bugs.winehq.org/show_bug.cgi?id=32010
Colin Wetherbee cww@denterprises.org changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |cww@denterprises.org
--- Comment #7 from Colin Wetherbee cww@denterprises.org --- Confirming Xen's comment: the GW2 launcher freezes X on a 64-bit wineprefix.
Wine 1.9.15
https://bugs.winehq.org/show_bug.cgi?id=32010
Patrick Rudolph patrick1804@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |patrick1804@web.de
--- Comment #8 from Patrick Rudolph patrick1804@web.de --- It calls UpdateLayeredWindow as fast as possible, which causes high load in X server and kernel. A possible solution would be to use dirty tracking or only update the layered window on next Vsync.
https://bugs.winehq.org/show_bug.cgi?id=32010
winetest@luukku.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |winetest@luukku.com
--- Comment #9 from winetest@luukku.com --- (In reply to Patrick Rudolph from comment #8)
It calls UpdateLayeredWindow as fast as possible, which causes high load in X server and kernel. A possible solution would be to use dirty tracking or only update the layered window on next Vsync.
Could you also share you opinion at bug 37959?
https://bugs.winehq.org/show_bug.cgi?id=32010
--- Comment #10 from Patrick Rudolph patrick1804@web.de --- After further investigations: UpdateLayeredWindow uses software fallback to blend a layered window using blend_rect_8888 function. That causes high load in the launcher process. It would be nice to let X do the blending instead.
After blending the result is put into a pixmap and flushed to X11 using x11drv_surface_flush.
x11drv_surface_flush calls update_surface_region which causes high load, too. It iterates over the whole surface to find the shape borders.
After that X11DRV_GetRegionData and XShapeCombineRectangles is called. It looks like this causes glamor/X11 to do a flush and stall until GPU finishes rendering. It then locks the framebuffer to read back and combine the pixmaps. This causes high load in X and the kernel as it does busy waiting.
By commenting the XShapeCombineRectangles code in x11drv_surface_flush, the load is reduced and X11 runs smooth. The mouse is also visible.
Not sure if this a X11 bug or wine bug.
https://bugs.winehq.org/show_bug.cgi?id=32010
--- Comment #11 from winetest@luukku.com --- Really irritating bug. This is basically blocking installing the game now...
wine 2.0.rc3 and staging 2.0rc3.
https://bugs.winehq.org/show_bug.cgi?id=32010
Thomas Kowaliczek linuxdonald@posteo.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |linuxdonald@posteo.de
https://bugs.winehq.org/show_bug.cgi?id=32010
--- Comment #12 from Thomas Kowaliczek linuxdonald@posteo.de --- i Have this bug to on arch linux with wine-staging. I hope it will be maybe fixed for wine 2.0.
https://bugs.winehq.org/show_bug.cgi?id=32010
--- Comment #13 from winetest@luukku.com --- Patrick do you have any idea how to fix this? Or could you even show how you worked out the bug? Seeing it in source code could help forming patch.
https://bugs.winehq.org/show_bug.cgi?id=32010
yhonay@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |yhonay@gmail.com
https://bugs.winehq.org/show_bug.cgi?id=32010
jon@moozaad.co.uk changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jon@moozaad.co.uk
--- Comment #14 from jon@moozaad.co.uk --- Workaround to the patcher window hang is to bypass it at the command line.
wine Gw2-64.exe -email bob@examaple.com -password zyxyzyxz -autologin -nopatchui
https://bugs.winehq.org/show_bug.cgi?id=32010
--- Comment #15 from winetest@luukku.com --- This bug is missing download word and url field should be filled.
https://account.arena.net/welcome
Tried 32bit windows version.
After launching the exe in fresh 32bit prefix pc came really non-responsive. I killed wine from another session.
wine 2.6.