http://bugs.winehq.org/show_bug.cgi?id=10778
Summary: Gothic3 crashs after warp Product: Wine Version: CVS/GIT Platform: PC-x86-64 URL: http://www.gothic3.com/index.php?do=09709911610511111006 1109101100105097 OS/Version: Linux Status: UNCONFIRMED Severity: enhancement Priority: P2 Component: wine-misc AssignedTo: wine-bugs@winehq.org ReportedBy: kgbricola@web.de
After taking a "teleporter" (in German "Teleportstein") Gothic3 crashes with this error:
err:seh:setup_exception stack overflow 0 bytes in thread 0025 eip 7e606e13 esp 6583e000 stack 0x6583e000-0x6604e000 err:ntdll:RtlpWaitForCriticalSection section 0x7e67ee68 "d3d9_main.c: d3d9_cs" wait timed out in thread 0010, blocked by 0025, retrying (60 sec)
My sys: Fedora7 64bit, Geforce 8800GTS, Driver: 100.14.19
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #1 from Rico kgbricola@web.de 2007-12-15 10:46:40 --- Created an attachment (id=9635) --> (http://bugs.winehq.org/attachment.cgi?id=9635) Gothic3 warp crash log
The log file to the post #0.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #2 from Rico kgbricola@web.de 2007-12-15 13:05:47 --- I'd like to look at the source of the problem ... but after I run this WINEDEBUG=+relay wine Gothic3.exe
an error message popped up (with SmartHeapLibrary -> MEM_BAD_POINTER) and the game exits. Is there a workaround for this MEM_BAD_POINTER bug?
http://bugs.winehq.org/show_bug.cgi?id=10778
Norbert Lataille nonal@freesurf.fr changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |nonal@freesurf.fr
--- Comment #3 from Norbert Lataille nonal@freesurf.fr 2007-12-16 14:16:46 --- Hum,
Something I forgot to ask. Does this bug occur after a "long" play time ? I've got similar crashes, when the game RSS reaches 1/1,5Gb. It is possible that this is only a consequence of wine leaking memory (VertexDecl leaking).
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #4 from Rico kgbricola@web.de 2007-12-17 05:59:15 --- Crashes after 10sec (or so) ... the time I need to take a teleporter. Output from top: VIRT:3911m RES:975m SHR:27m (low details) There are NO OUT_OF_MEMORY errors in the console.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #5 from Rico kgbricola@web.de 2007-12-17 07:02:26 --- Could be the same bug because sometimes I get a the same error message!
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #6 from Rico kgbricola@web.de 2007-12-17 07:38:34 --- After trying a while I managed to teleport in a new game to the first city. (Running to the table, take the teleporter and teleport. So this has nothing to do width the WARP. Looks like the same error as the other one!
http://bugs.winehq.org/show_bug.cgi?id=10778
Rico kgbricola@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Gothic3 crashs after warp |Gothic3 crashs after warp | |(VIRTmem > 4096MB?)
--- Comment #7 from Rico kgbricola@web.de 2008-02-02 13:42:43 --- After trying a lot around the game seems to crash when VIRT (output from top) > 4096MB. So it is not related to the warp. It crashs while the game loads new map data (warp to another location).
The log isn't really useful because the crash happens randomly. It depends on "where the memory is out".
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #8 from Gregor Münch greg87@online.de 2008-02-10 13:56:38 --- Please try the new patch 1.6. In the changelog is a lot about memory leaks listed which should be fixed now. http://www.worldofgothic.de/dl/index.php?go=downloads&file_id=317
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #9 from Rico kgbricola@web.de 2008-02-10 15:19:34 --- After warping around and running across the map the game behaves as before the patch. But it is much better.
The patch solves the issue a little bit, but not complete ... for the short try (20min) I am at 4087m (VIRT) and the game is unplayable slow (about 5min long). Then the game crashes after the line err:ntdll:RtlpWaitForCriticalSection section 0x7e23da60 "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 0026, blocked by 001e, retrying (60 sec).
I'll give it another try later and report if something interesting happened.
http://bugs.winehq.org/show_bug.cgi?id=10778
Florian mcflow-forum@gmx.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |mcflow-forum@gmx.net
--- Comment #10 from Florian mcflow-forum@gmx.net 2008-03-14 08:54:34 --- (In reply to comment #9)
After warping around and running across the map the game behaves as before the patch. But it is much better.
The patch solves the issue a little bit, but not complete ... for the short try (20min) I am at 4087m (VIRT) and the game is unplayable slow (about 5min long). Then the game crashes after the line err:ntdll:RtlpWaitForCriticalSection section 0x7e23da60 "x11drv_main.c: X11DRV_CritSection" wait timed out in thread 0026, blocked by 001e, retrying (60 sec).
I'll give it another try later and report if something interesting happened.
I can confirm this. I get this, too. There are a lot of this messages: err:d3d:CreateIndexBufferVBO Failed to initialize the index buffer with error GL_OUT_OF_MEMORY (0x505) and this: fixme:ntdll:FILE_GetNtStatus Converting errno 12 to STATUS_UNSUCCESSFUL
Gothic3 crashes with a Microsoft Visual++ error then.
http://bugs.winehq.org/show_bug.cgi?id=10778
SuSE-Fighter alpha2002b@aol.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |alpha2002b@aol.com
--- Comment #11 from SuSE-Fighter alpha2002b@aol.com 2008-03-17 11:42:07 --- im not shure... maybe it help ??
http://www.nvidia.de/object/linux_display_ia32_169.12_de.html
" Weiter verbessertes Handling von Out-of-Memory-Problemen bei Verwendung von GLX_EXT_texture_from_pixmap. "
http://bugs.winehq.org/show_bug.cgi?id=10778
SuSE-Fighter alpha2002b@aol.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|alpha2002b@aol.com |
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #12 from Florian mcflow-forum@gmx.net 2008-03-23 15:50:17 --- (In reply to comment #11)
im not shure... maybe it help ??
http://www.nvidia.de/object/linux_display_ia32_169.12_de.html
" Weiter verbessertes Handling von Out-of-Memory-Problemen bei Verwendung von GLX_EXT_texture_from_pixmap. "
Okay, I should have said that I already upgraded to this driver.
http://bugs.winehq.org/show_bug.cgi?id=10778
Marcin ergo14@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Ever Confirmed|0 |1
--- Comment #13 from Marcin ergo14@gmail.com 2008-04-20 06:31:58 --- *** This bug has been confirmed by popular vote. ***
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #14 from Rico kgbricola@web.de 2008-06-08 14:53:46 --- Created an attachment (id=13820) --> (http://bugs.winehq.org/attachment.cgi?id=13820) workaround for this issue
I tried the game with the attached patch and I couldn't get it crashing. Probably someone could give it a try? This workaround changes the size of memory which wine allocates. Is there a reason why this value (the original one) is so big?
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #15 from Florian mcflow-forum@gmx.net 2008-06-29 06:10:17 --- (In reply to comment #14)
Created an attachment (id=13820)
--> (http://bugs.winehq.org/attachment.cgi?id=13820) [details]
workaround for this issue
I tried the game with the attached patch and I couldn't get it crashing. Probably someone could give it a try? This workaround changes the size of memory which wine allocates. Is there a reason why this value (the original one) is so big?
True, I couldn't make the game crash, too. I tried various fireball spells, teleport scrolls and moving around a lot but it did not crash.
http://bugs.winehq.org/show_bug.cgi?id=10778
Mariusz magmp1@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |magmp1@gmail.com
--- Comment #16 from Mariusz magmp1@gmail.com 2008-07-05 02:05:02 --- (In reply to comment #14)
Created an attachment (id=13820)
--> (http://bugs.winehq.org/attachment.cgi?id=13820) [details]
workaround for this issue
I tried the game with the attached patch and I couldn't get it crashing. Probably someone could give it a try? This workaround changes the size of memory which wine allocates. Is there a reason why this value (the original one) is so big?
How should I patch it? With p0 or p1?
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #17 from Mikael Åkersund mikael.akersund@bigfoot.com 2008-10-26 12:48:22 --- (In reply to comment #16)
(In reply to comment #14)
Created an attachment (id=13820)
--> (http://bugs.winehq.org/attachment.cgi?id=13820) [details] [details]
workaround for this issue
I tried the game with the attached patch and I couldn't get it crashing. Probably someone could give it a try? This workaround changes the size of memory which wine allocates. Is there a reason why this value (the original one) is so big?
How should I patch it? With p0 or p1?
With -p1
I would also like to add that Bioshock(Steam Demo) suffers from a very similar problem. At least the above patch removed the crashes for me.
http://bugs.winehq.org/show_bug.cgi?id=10778
Vitaliy Margolen vitaliy@kievinfo.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jorgen.hedlund@gmail.com
--- Comment #18 from Vitaliy Margolen vitaliy@kievinfo.com 2008-11-22 11:27:09 --- *** Bug 16131 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #19 from JH jorgen.hedlund@gmail.com 2008-11-22 13:16:27 --- Ok, I opened the bug 16131 (World of Warcraft related) that is said to be a duplicate of this bug. I'm not so sure about it but I'll accept the judgment.
I've tried some different stuff that I've detailed in the other bug.
No patch has been successful for me yet and I'm starting to wonder whether it's an addon bug that's causing this. I'll search some more...
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #20 from Roderick Colenbrander thunderbird2k@gmx.net 2008-11-25 12:57:58 --- I want to point out that the mmap patch by Alexandre attached to bug 13335 is the proper solution for this issue. There are some issues with it which need to be resolved first before it makes it into Wine. I can't say when it will enter it as it sounded that they were hard to fix even for Alexandre.
http://bugs.winehq.org/show_bug.cgi?id=10778
Adys adys.wh+winehqdotorg@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |adys.wh+winehqdotorg@gmail.c | |om
--- Comment #21 from Adys adys.wh+winehqdotorg@gmail.com 2008-12-06 22:34:41 --- (In reply to comment #20)
I want to point out that the mmap patch by Alexandre attached to bug 13335 is the proper solution for this issue. There are some issues with it which need to be resolved first before it makes it into Wine. I can't say when it will enter it as it sounded that they were hard to fix even for Alexandre.
I tried the new mmap patch, but I couldn't get World of Warcraft not to crash (see dup bug 16131). I had to use the preloader.c patch from here too, and it'll stil crash after a while.
http://bugs.winehq.org/show_bug.cgi?id=10778
DL taedium_vitae@eml.cc changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |taedium_vitae@eml.cc
--- Comment #22 from DL taedium_vitae@eml.cc 2008-12-28 03:29:45 --- This problem also occurs with Fallout 3 and Stalker (with dynamic lighting enabled).Fallout 3 only crashes occasionally and usually during indoor areas but Stalker crashes almost immediatly.Both show massive VIRT memory usage(4000MB or so), so I assume it's the same issue.I've tried the mmap patch but it causes massive slowdowns, like others have mentioned.
http://bugs.winehq.org/show_bug.cgi?id=10778
Anders Aagaard aagaande@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |aagaande@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=10778
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Version|CVS/GIT |unspecified
--- Comment #23 from Austin English austinenglish@gmail.com 2009-01-18 03:47:13 --- Removing deprecated CVS/GIT version tag. Please retest in current git. If the bug is still present in today's wine, but was not present in some earlier version of wine, please update version field to earliest known version of wine that had the bug. Thanks!
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #24 from Adys adys.wh+winehqdotorg@gmail.com 2009-01-18 16:49:25 --- (In reply to comment #23)
Removing deprecated CVS/GIT version tag. Please retest in current git. If the bug is still present in today's wine, but was not present in some earlier version of wine, please update version field to earliest known version of wine that had the bug. Thanks!
This is still happening in latest Git.
http://bugs.winehq.org/show_bug.cgi?id=10778
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |tom.weingarten@gmail.com
--- Comment #25 from Austin English austinenglish@gmail.com 2009-01-23 09:03:02 --- *** Bug 15290 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=10778
Andrew Yates andrewyates@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |andrewyates@gmail.com
http://bugs.winehq.org/show_bug.cgi?id=10778
Xavier Vachon xvachon@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |xvachon@gmail.com
--- Comment #26 from Xavier Vachon xvachon@gmail.com 2009-02-09 07:50:37 --- I have this error when I attempt to apply this patch in a clean wine-git.
xavier@localhost ~/wine-git $ patch -p1 < memory.patch patching file loader/preloader.c Hunk #1 FAILED at 110. 1 out of 1 hunk FAILED -- saving rejects to file loader/preloader.c.rej
Anything wrong in the command I have issued?
http://bugs.winehq.org/show_bug.cgi?id=10778
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |skully@gmx.ch
--- Comment #27 from Austin English austinenglish@gmail.com 2009-02-10 00:30:43 --- *** Bug 17330 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=10778
Rico kgbricola@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Attachment #13820|0 |1 is obsolete| |
--- Comment #28 from Rico kgbricola@web.de 2009-02-10 11:15:06 --- Created an attachment (id=19364) --> (http://bugs.winehq.org/attachment.cgi?id=19364) new workaround for this issue
Update of the patch, this should apply to current git (3e6d9558b8c119282fc976778762f4de1dc4fdab).
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #29 from Mikael Åkersund mikael.akersund@bigfoot.com 2009-02-22 14:53:23 --- (In reply to comment #28)
Created an attachment (id=19364)
--> (http://bugs.winehq.org/attachment.cgi?id=19364) [details]
new workaround for this issue
Update of the patch, this should apply to current git (3e6d9558b8c119282fc976778762f4de1dc4fdab).
Excellent! I've been using this workaround for quite some time now to get Fallout3 really stable. Unless there's a Really Good Reason(©) (ie some critical app needs it) that Wine reserves 0x5fef0000 bytes of low memory area I strongly urge you to send in a patch to wine-patches@winehq.org
http://bugs.winehq.org/show_bug.cgi?id=10778
Julien Etienne julien.etienne@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |julien.etienne@gmail.com
--- Comment #30 from Julien Etienne julien.etienne@gmail.com 2009-02-24 16:49:29 --- I tried the provided patch on the wine-git, unfortunately it only slows the 4GB limit... It is still reached at some point whatever game I use.
So I can confirm the 4GB issue is still present, and it is not solved by the patch provided.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #31 from Rico kgbricola@web.de 2009-03-10 05:00:18 --- Possible related nvidia forum tread http://www.nvnews.net/vbulletin/showthread.php?t=127984 , because I guess this happens only on machines with 4GB ram or more.
Did anyone have the problem with less memory?
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #32 from Adys adys.wh+winehqdotorg@gmail.com 2009-03-10 06:01:29 --- (In reply to comment #31)
Possible related nvidia forum tread http://www.nvnews.net/vbulletin/showthread.php?t=127984 , because I guess this happens only on machines with 4GB ram or more.
Did anyone have the problem with less memory?
Yes. 2GB here, WoW crashes without the preloader patch. cf bug 16131. (At least as of ~2 months ago. It's been happening less and less lately though, I'll try without the patch when I'll get the occasion.)
http://bugs.winehq.org/show_bug.cgi?id=10778
Denis Zhdanov altwazar@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |altwazar@gmail.com
--- Comment #33 from Denis Zhdanov altwazar@gmail.com 2009-03-11 02:38:44 --- (In reply to comment #31)
Possible related nvidia forum tread http://www.nvnews.net/vbulletin/showthread.php?t=127984 , because I guess this happens only on machines with 4GB ram or more.
Did anyone have the problem with less memory?
Yes. With mem=3g and preloader patch World of Warcraft stil crash after a while. But with it i can play much longer.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #34 from Julien Etienne julien.etienne@gmail.com 2009-03-11 03:07:40 --- (In reply to comment #33)
(In reply to comment #31)
Possible related nvidia forum tread http://www.nvnews.net/vbulletin/showthread.php?t=127984 , because I guess this happens only on machines with 4GB ram or more.
Did anyone have the problem with less memory?
Yes. With mem=3g and preloader patch World of Warcraft stil crash after a while. But with it i can play much longer.
I have 6 GB ram, I experience the issue if I boot linux as is. As told above the provided patch doesn't help, and after reading it I don't see how it could solve anything, but I would be glad to have an explanation for my understanding.
Using mem=3G or mem=4G, the issue disappears completely even after 4 hours of World of Warcraft.
I have reproduced the issue with the minimal test case provided on nvnews forums (see comment #33), it looks like it is related to using a 32bits opengl program in a 64 bits OS. Even glxgears (32 bits) shows the issue. For me the issue could be related to the fact that the nvidia driver uses ram for texture above the 4G if such ram is available, leading to issues when running in a 32bits userspace. Anyway it means the 32bits implementation of opengl is faulty on 64bits hosts. Maybe its just the wrapper, maybe its the driver, but its probably not wine.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #35 from DL taedium_vitae@eml.cc 2009-03-11 08:24:47 --- (In reply to comment #34)
(In reply to comment #33)
(In reply to comment #31)
Possible related nvidia forum tread http://www.nvnews.net/vbulletin/showthread.php?t=127984 , because I guess this happens only on machines with 4GB ram or more.
Did anyone have the problem with less memory?
Yes. With mem=3g and preloader patch World of Warcraft stil crash after a while. But with it i can play much longer.
I have 6 GB ram, I experience the issue if I boot linux as is. As told above the provided patch doesn't help, and after reading it I don't see how it could solve anything, but I would be glad to have an explanation for my understanding.
Using mem=3G or mem=4G, the issue disappears completely even after 4 hours of World of Warcraft.
I have reproduced the issue with the minimal test case provided on nvnews forums (see comment #33), it looks like it is related to using a 32bits opengl program in a 64 bits OS. Even glxgears (32 bits) shows the issue. For me the issue could be related to the fact that the nvidia driver uses ram for texture above the 4G if such ram is available, leading to issues when running in a 32bits userspace. Anyway it means the 32bits implementation of opengl is faulty on 64bits hosts. Maybe its just the wrapper, maybe its the driver, but its probably not wine.
The problem also occurs with a 32 bit OS, so it's not 64bit specific.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #36 from Julien Etienne julien.etienne@gmail.com 2009-03-11 08:44:02 --- (In reply to comment #35)
The problem also occurs with a 32 bit OS, so it's not 64bit specific.
I found no reports of this bug occuring on a 32bit linux OS, and at the moment all the investigations are pointing toward a 32bit userland vs 64 bit OS/driver issue.
I validated that the bug does not occur with a 32bit live cd, whereas it occurs with the 64bit one (same hardware). If I boot the 64bit live cd with mem=4G the bug does not appear. So for me it can not be triggered by a 32bit OS or at least I did not succeed in reproducing it.
So far it looks like it is linked to the physical memory allocation above 2^32.
Could you please give me pointers to a 32bit OS reproduction of this bug as it could help the investigation ? Thanks.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #37 from Skully skully@gmx.ch 2009-03-11 09:17:26 --- I am using a 32bit os (debian lenny). Using latest wine and i have 4 gb memory. (3.2 used) My WoW does crash after a while with a crit error "not enough memory". See here: http://bugs.winehq.org/show_bug.cgi?id=17330
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #38 from Julien Etienne julien.etienne@gmail.com 2009-03-11 11:05:55 --- (In reply to comment #37)
I am using a 32bit os (debian lenny). Using latest wine and i have 4 gb memory. (3.2 used) My WoW does crash after a while with a crit error "not enough memory". See here: http://bugs.winehq.org/show_bug.cgi?id=17330
I am not sure it is the same issue.
In the present bug the memory limit reached is always 4GB, in your case you show a WoW.exe using only 1.6GB. While it does not look normal, it is far from the 4GB I get when starting WoW.exe (even with mem=3GB).
Could you try to reproduce it with the code provided here (leaktest.c.txt): http://www.nvnews.net/vbulletin/showpost.php?p=1945813&postcount=36
If you cannot reproduce the memory leak that way, it is definetely 2 distinct issues. Thanks for your feedback.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #39 from Skully skully@gmx.ch 2009-03-11 12:06:24 --- Tried it for 5m now and the memory usage stays the same, gonna let it run a bit longer to be sure but seems my opengl isnt leaking.
http://bugs.winehq.org/show_bug.cgi?id=10778
Frederic kaempfer@mathematik.uni-marburg.de changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |kaempfer@mathematik.uni- | |marburg.de
--- Comment #40 from Frederic kaempfer@mathematik.uni-marburg.de 2009-03-31 12:24:42 --- The issue seems to be fixed with the newest NVIDIA drivers (180.44). The leaktest doesn't leak anymore and I can play World of Warcraft for a long time without any problems. I'm using wine 1.1.16 including the suggested workaround patch.
Other users are also reporting this problem to be fixed: http://www.nvnews.net/vbulletin/showthread.php?t=127984&page=5
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #41 from Rico kgbricola@web.de 2009-04-01 13:40:42 --- Yes, the driver 180.44 for nvidia cards is nice. The memory leak in their driver is fixed.
But I could also reproduce this crash with this driver and wine-1.1.18-119-g276c7a3. So the bug is still there. Also with my patch applied, I couldn't reproduce the crash on a short try.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #42 from Julien Etienne julien.etienne@gmail.com 2009-04-01 15:41:16 --- Issue fixed for me with nvidia driver 180.44 No more memory leak, wine runs great for hours whatever opengl game I launch.
http://bugs.winehq.org/show_bug.cgi?id=10778
Ferry Landzaat wine@mephistonet.nl changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |wine@mephistonet.nl
--- Comment #43 from Ferry Landzaat wine@mephistonet.nl 2009-04-02 11:43:25 --- I'm afraid i have to confirm the crashes did not go away for me with 180.44. I just installed the driver today, rebooted, the nvidia settings panel shows the right driver version. WoW still gives me random polygons when staying in dalaran for too long. This is on a 32 bit system (on 64 bit hardware, but fully 32 bit OS), with 4GB of ram using PAE-enabled kernel. I had the same issue with 2GB of ram.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #44 from Ferry Landzaat wine@mephistonet.nl 2009-04-02 11:46:40 --- I'm afraid i have to confirm the crashes did not go away for me with 180.44. I just installed the new driver today, rebooted, and the nvidia settings panel shows the right driver version. WoW still gives me random polygons after going to dalaran too often. This is on a 32 bit system (on 64 bit hardware, but fully 32 bit OS), with 4GB of ram using PAE-enabled kernel. I had the same issue with 2GB of ram. I'm using a stock wine 1.1.15, the one that came with my distro (fedora 10).
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #45 from Ferry Landzaat wine@mephistonet.nl 2009-04-02 11:54:59 --- Hmmz, sorry for double-post... the site was so slow that i cancelled it to make a few changes. The first post can be deleted if possible...
http://bugs.winehq.org/show_bug.cgi?id=10778
Julien Etienne julien.etienne@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC|julien.etienne@gmail.com |
http://bugs.winehq.org/show_bug.cgi?id=10778
Marcus Møller koenmarcus@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |koenmarcus@hotmail.com
--- Comment #46 from Marcus Møller koenmarcus@hotmail.com 2009-04-10 05:53:34 --- I've just patched Wine 1.1.18 with this patch, but I'm still having issues with WoW; It still keeps making deadlock (or hardlock, I dunno what you call it) for some reason.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #47 from Marcus Møller koenmarcus@hotmail.com 2009-04-10 06:04:10 --- (In reply to comment #46)
I've just patched Wine 1.1.18 with this patch, but I'm still having issues with WoW; It still keeps making deadlock (or hardlock, I dunno what you call it) for some reason.
This is more like an edit: I've got GeForce 8800GT and nVidia driver 180.44, but it's not fixed. I'm desperate for getting it fixed.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #47 from Marcus Møller koenmarcus@hotmail.com 2009-04-10 06:04:10 --- (In reply to comment #46)
I've just patched Wine 1.1.18 with this patch, but I'm still having issues with WoW; It still keeps making deadlock (or hardlock, I dunno what you call it) for some reason.
This is more like an edit: I've got GeForce 8800GT and nVidia driver 180.44, but it's not fixed. I'm desperate for getting it fixed.
--- Comment #48 from Jeff Zaroyko jeffz@jeffz.name 2009-04-10 06:49:30 --- (In reply to comment #46)
I've just patched Wine 1.1.18 with this patch, but I'm still having issues with WoW; It still keeps making deadlock (or hardlock, I dunno what you call it) for some reason.
deadlock/hardlock, that's not what this bug is about
http://bugs.winehq.org/show_bug.cgi?id=10778
Alex maxpayne1986@yandex.ru changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |maxpayne1986@yandex.ru
--- Comment #47 from Marcus Møller koenmarcus@hotmail.com 2009-04-10 06:04:10 --- (In reply to comment #46)
I've just patched Wine 1.1.18 with this patch, but I'm still having issues with WoW; It still keeps making deadlock (or hardlock, I dunno what you call it) for some reason.
This is more like an edit: I've got GeForce 8800GT and nVidia driver 180.44, but it's not fixed. I'm desperate for getting it fixed.
--- Comment #48 from Jeff Zaroyko jeffz@jeffz.name 2009-04-10 06:49:30 --- (In reply to comment #46)
I've just patched Wine 1.1.18 with this patch, but I'm still having issues with WoW; It still keeps making deadlock (or hardlock, I dunno what you call it) for some reason.
deadlock/hardlock, that's not what this bug is about
--- Comment #49 from Alex maxpayne1986@yandex.ru 2009-04-10 16:36:46 --- Build wine today from sources, bug is still there. I build patched wine, with [url=http://bugs.winehq.org/attachment.cgi?id=19364%5Dthis%5B/url] workaround. With it, WoW virtual memory usage just grows up slower than without it.
OS Fedora Core 10 x64
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #50 from Alex maxpayne1986@yandex.ru 2009-04-10 16:38:43 --- Oops, sorry for bad link >.< Here is good one: http://bugs.winehq.org/attachment.cgi?id=19364
http://bugs.winehq.org/show_bug.cgi?id=10778
Tony Murray murraytony@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |murraytony@gmail.com
--- Comment #51 from Tony Murray murraytony@gmail.com 2009-05-23 00:49:16 --- I'm still experiencing this bug with World of Warcraft. I can have top open in one window and the instant the VIRT category for WoW.exe reaches >4048 it crashes.
http://bugs.winehq.org/show_bug.cgi?id=10778
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |vallidor@gangrenegang.com
--- Comment #52 from Jeff Zaroyko jeffz@jeffz.name 2009-05-23 09:30:08 --- *** Bug 14395 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=10778
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |vallidor@gangrenegang.com
zitzengallenfliege@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zitzengallenfliege@hotmail. | |com
--- Comment #52 from Jeff Zaroyko jeffz@jeffz.name 2009-05-23 09:30:08 --- *** Bug 14395 has been marked as a duplicate of this bug. ***
--- Comment #53 from zitzengallenfliege@hotmail.com 2009-06-25 12:59:33 --- See also this Bug (http://bugs.winehq.org/show_bug.cgi?id=13335#c178). I tried it with the newest version from GIT, without any patches and the situation seems to have improved a lot. No crashes so far, I'll keep testing.
http://bugs.winehq.org/show_bug.cgi?id=10778
Jeff Zaroyko jeffz@jeffz.name changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |vallidor@gangrenegang.com
zitzengallenfliege@hotmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |zitzengallenfliege@hotmail. | |com
--- Comment #52 from Jeff Zaroyko jeffz@jeffz.name 2009-05-23 09:30:08 --- *** Bug 14395 has been marked as a duplicate of this bug. ***
--- Comment #53 from zitzengallenfliege@hotmail.com 2009-06-25 12:59:33 --- See also this Bug (http://bugs.winehq.org/show_bug.cgi?id=13335#c178). I tried it with the newest version from GIT, without any patches and the situation seems to have improved a lot. No crashes so far, I'll keep testing.
--- Comment #54 from Xavier Vachon xvachon@gmail.com 2009-07-05 11:31:51 --- As of latest git 1.1.25, the preloader.patch hack does not compile.
http://bugs.winehq.org/show_bug.cgi?id=10778
--- Comment #55 from Jerome Leclanche adys.wh@gmail.com 2009-07-05 14:28:58 --- (In reply to comment #54)
As of latest git 1.1.25, the preloader.patch hack does not compile.
This bug really is a duplicate of bug 13335; you shouldn't need the patch anymore.
http://bugs.winehq.org/show_bug.cgi?id=10778
Rico kgbricola@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |19219
--- Comment #56 from Rico kgbricola@web.de 2009-07-11 07:32:18 --- I could not test if it is fixed, because the game crashes on the loading screen after commit 09712593c8496be5e952b7316099f9eed5043203, which solved bug 13335 . So I'm not 100% sure that it is a dupe. At least the same patch didn't solve the problem!
The new regression is bug 19219 . So we have to wait until this bug is fixed. Also note, that the preloader workaround doesn't solve the problem anymore (after the regression mentioned above).
http://bugs.winehq.org/show_bug.cgi?id=10778
Rico kgbricola@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |19219 Status|NEW |RESOLVED Resolution| |FIXED
--- Comment #56 from Rico kgbricola@web.de 2009-07-11 07:32:18 --- I could not test if it is fixed, because the game crashes on the loading screen after commit 09712593c8496be5e952b7316099f9eed5043203, which solved bug 13335 . So I'm not 100% sure that it is a dupe. At least the same patch didn't solve the problem!
The new regression is bug 19219 . So we have to wait until this bug is fixed. Also note, that the preloader workaround doesn't solve the problem anymore (after the regression mentioned above).
--- Comment #57 from Rico kgbricola@web.de 2009-08-07 13:51:28 --- It seems to be fixed by commit 09712593c8496be5e952b7316099f9eed5043203 (bug 13335) and c10bdbefd69786846b035d1c38de3052bed67875 (bug 19219).
http://bugs.winehq.org/show_bug.cgi?id=10778
Rico kgbricola@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |19219 Status|NEW |RESOLVED Resolution| |FIXED
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #56 from Rico kgbricola@web.de 2009-07-11 07:32:18 --- I could not test if it is fixed, because the game crashes on the loading screen after commit 09712593c8496be5e952b7316099f9eed5043203, which solved bug 13335 . So I'm not 100% sure that it is a dupe. At least the same patch didn't solve the problem!
The new regression is bug 19219 . So we have to wait until this bug is fixed. Also note, that the preloader workaround doesn't solve the problem anymore (after the regression mentioned above).
--- Comment #57 from Rico kgbricola@web.de 2009-08-07 13:51:28 --- It seems to be fixed by commit 09712593c8496be5e952b7316099f9eed5043203 (bug 13335) and c10bdbefd69786846b035d1c38de3052bed67875 (bug 19219).
--- Comment #58 from Alexandre Julliard julliard@winehq.org 2009-08-21 12:05:55 --- Closing bugs fixed in 1.1.28.
http://bugs.winehq.org/show_bug.cgi?id=10778
Rico kgbricola@web.de changed:
What |Removed |Added ---------------------------------------------------------------------------- Depends on| |19219 Status|NEW |RESOLVED Resolution| |FIXED
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #56 from Rico kgbricola@web.de 2009-07-11 07:32:18 CDT --- I could not test if it is fixed, because the game crashes on the loading screen after commit 09712593c8496be5e952b7316099f9eed5043203, which solved bug 13335 . So I'm not 100% sure that it is a dupe. At least the same patch didn't solve the problem!
The new regression is bug 19219 . So we have to wait until this bug is fixed. Also note, that the preloader workaround doesn't solve the problem anymore (after the regression mentioned above).
--- Comment #57 from Rico kgbricola@web.de 2009-08-07 13:51:28 CDT --- It seems to be fixed by commit 09712593c8496be5e952b7316099f9eed5043203 (bug 13335) and c10bdbefd69786846b035d1c38de3052bed67875 (bug 19219).
--- Comment #58 from Alexandre Julliard julliard@winehq.org 2009-08-21 12:05:55 CDT --- Closing bugs fixed in 1.1.28.
-
wine-bugs＠winehq.org