http://bugs.winehq.org/show_bug.cgi?id=7229
JH jorgen.hedlund@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jorgen.hedlund@gmail.com
--- Comment #21 from JH jorgen.hedlund@gmail.com 2008-01-19 07:11:22 --- I can confirm that this bug is still in effect.
Some info: wine-0.9.53 World of Warcraft Client Patch 2.3.2
Linux version 2.6.22-14-generic (buildd@terranova) (gcc version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #1 SMP Tue Dec 18 08:02:57 UTC 2007 (Ubuntu 2.6.22-14.47-generic)
CPU0: AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ stepping 03 CPU1: AMD Athlon(tm) 64 X2 Dual Core Processor 6400+ stepping 03
I often see this problem in Battlegrounds and especially when I encounter players from other servers. As I run WoW from the prompt I can easily alt-tab and ctrl-c wine to restart it all (this often prevents me from being killed btw, don't ask me why ;-)
Other cases are when zoning.
This suggests what's being discussed in #13 & #14 and textureloading thingies.
I've not yet tried the schedtool stuff (#16) as I don't know how to revert those changes if it doesn't help :-) (suggestions?)
In <wow install dir>/Logs/ there are logfiles that displays what WoW actually detects, these I can attach if needed.
Note: A start->login->exit wow yields a 2.3GB logfile when using WINEDEBUG=+all.