http://bugs.winehq.org/show_bug.cgi?id=15926
Summary: World of Warcraft: Memory leak on new login screen, X crashing Product: Wine Version: 1.1.7 Platform: PC-x86-64 URL: http://www.worldofwarcraft.com OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: opengl AssignedTo: wine-bugs@winehq.org ReportedBy: adys.wh+winehqdotorg@gmail.com
Commonly reported behaviour from other wine users. Does not happen under Windows.
The new Wrath of the Lich King login screen suffers from extreme performance problems. Apart from it being slower than the old one, it also gets slower on every WoW reboot. Using another WINEPREFIX does not fix the problem. Killing all wine and related processes does not fix the problem either. Restarting X is the only way to work this around.
After 5-6 reboots, WoW does not start and X instantly crashes. 100% reproducible.
Using OpenGL engine, changing various settings in Config.wtf does not seem to have any effect.
http://bugs.winehq.org/show_bug.cgi?id=15926
--- Comment #1 from Adys adys.wh+winehqdotorg@gmail.com 2008-11-08 03:12:14 --- Pasted from bug 15925
Could users having this problem try this?
- Go in winecfg, graphics and disable pixel shaders
- In game, go in graphic options and disable Triple Buffering as well as Full Screen Glow
- Eventually, try disabling the GL_ARB_vertex_buffer_object extension with http://www.wowwiki.com/Wine_(software)#Registry_Tweak_for_FPS_Boost
For me, it fixed this bug as well as bug 15926 and bug 15927
http://bugs.winehq.org/show_bug.cgi?id=15926
Nephyrin zey Nephyrin@nephyrin.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Nephyrin@nephyrin.net
--- Comment #2 from Nephyrin zey Nephyrin@nephyrin.net 2008-11-08 21:34:58 --- This is *NOT* a login-screen only problem. I have had this very issue since 3.0 was released, with the whole game. It is shader (and possibly/probably nvidia) related.
Disabling pixel shaders in winecfg *seems to completely solve* this issue for me.
This seems to be a separate and distinct issue from the general FPS drop 3.0 brought on, though they could easily be confused. I have noticed a maybe ~10fps drop, which is probably just the new rendering engine vs a specific wine issue.
What happens:
The game will start, initially, just fine. After playing for a while, it will start to 'hiccup' - full FPS, but ~100ms freezes every few seconds, seemingly random.
I have a macro bound to "/script RestartGx();" which restart's WoW's rendering engine - this will solve the problem for a short while, usually only 10 minutes or so. The amount of time this buys me shrinks each time. Eventually it's unplayable. The hiccuping gets worse and worse.
Restarting WoW makes things better for a short time, but like above, less and less each time. Exiting WoW while this bug has been occuring causes CPU usage to stick at 100% for a full few minutes before WoW.exe finally leaves. Memory usage steadily declines during this period.
--> Eventually, no matter what, WoW is unplayable until a *Full X Restart*. Even if wine is completely closed. This heavily indicates some kind of nvidia trouble - I've tried 177.80, and 177.61.02 (OpenGL 3 dev release) versions, but not many others yet
Let me know if there's anything i can try or help test - I miss my pretty bloom effects :P
http://bugs.winehq.org/show_bug.cgi?id=15926
Roderick Colenbrander thunderbird2k@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |DUPLICATE
--- Comment #3 from Roderick Colenbrander thunderbird2k@gmx.net 2008-11-11 16:00:13 --- I'm marking this bug as a duplicate of 15925. Both are about massive performance problems in a new version of WoW and most likely they have the same cause.
*** This bug has been marked as a duplicate of bug 15925 ***
http://bugs.winehq.org/show_bug.cgi?id=15926
James Hawkins truiken@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #4 from James Hawkins truiken@gmail.com 2008-11-11 16:01:32 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=15926
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|CLOSED |UNCONFIRMED Resolution|DUPLICATE |
--- Comment #5 from Jerome Leclanche adys.wh@gmail.com 2009-06-18 09:53:22 --- Reopening. Bug 15925 has been fixed, and this problem still exists. However it only happens with compositing turned on.
http://bugs.winehq.org/show_bug.cgi?id=15926
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #6 from Jerome Leclanche adys.wh@gmail.com 2009-06-18 09:54:10 --- Seems safe to flag INVALID.
http://bugs.winehq.org/show_bug.cgi?id=15926
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Jerome Leclanche adys.wh@gmail.com 2009-06-18 09:54:22 --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=15926
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Keywords| |download
-
wine-bugs＠winehq.org