http://bugs.winehq.org/show_bug.cgi?id=16677
Summary: World of Warcraft WotLK crashes randomly after login Product: Wine Version: 1.1.11 Platform: PC-x86-64 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: tudor.prodan@gmail.com
WoW WotLK 3.0.2. After logging in it crashes randomly, usually in under a minute.
So far I've got two types of crashes based on the errors:
Type 1, most common, gives: *** glibc detected *** C:\WoW\WoW.exe: corrupted double-linked list: 0x62901b98 *** ======= Backtrace: ========= /lib32/libc.so.6[0xf7d17fe4] /lib32/libc.so.6[0xf7d1b092] /lib32/libc.so.6(__libc_calloc+0x288)[0xf7d1c348] /usr/lib32/libGLcore.so.1[0x7d5fa431] ======= Memory map: ======== 00000000-00110000 ---p 00000000 00:00 0 00110000-00220000 rwxp 00110000 00:00 0 00220000-00223000 rwxp 00220000 00:00 0 .. more lines here, trimmed
Type 2 gives: err:module:load_builtin_dll failed to load .so lib for builtin L"dbghelp.dll": /usr/bin/../lib32/wine/dbghelp.dll.so: failed to map segment from shared object: Cannot allocate memory
http://bugs.winehq.org/show_bug.cgi?id=16677
Antoine amarty@free.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |amarty@free.fr
--- Comment #1 from Antoine amarty@free.fr 2009-02-18 06:07:16 --- Hi
i have the same kind of crashed and it appears most of the time in Dalaran zone at the high traffic hours.
If i have well understand some posts it's maybe due to system having 4Gb ram or more. Because of the WoW 32 bit engine.
A workaround that works fine for me was to add a parameter on my boot string:
mem=3072M
With that the OS is only see the 3Gb of RAM, then Wine don't try to use more neither and it goes fine.
The problem is that you drop the amount of memory available for the wall system and not only Wine and Wow.
Is there a way to limit the amount of memory use for wine only or for a specific wine application for exemple ?
http://bugs.winehq.org/show_bug.cgi?id=16677
--- Comment #2 from Austin English austinenglish@gmail.com 2009-08-26 13:20:09 --- Is this still present in current (1.1.28 or newer) wine?
http://bugs.winehq.org/show_bug.cgi?id=16677
--- Comment #3 from Antoine amarty@free.fr 2009-08-28 02:39:06 --- I have test with the 1.1.28, and i have no more issue very stable version
http://bugs.winehq.org/show_bug.cgi?id=16677
Dmitry Timoshkov dmitry@codeweavers.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |FIXED
--- Comment #4 from Dmitry Timoshkov dmitry@codeweavers.com 2009-08-28 05:46:54 --- Reported fixed.
http://bugs.winehq.org/show_bug.cgi?id=16677
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #5 from Alexandre Julliard julliard@winehq.org 2009-09-02 14:21:07 --- Closing bugs fixed in 1.1.29.