http://bugs.winehq.org/show_bug.cgi?id=24826
Summary: WoW 4.x D3D: Out of Memory errors with detailed shadows Product: Wine Version: 1.3.5 Platform: x86 OS/Version: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown AssignedTo: wine-bugs@winehq.org ReportedBy: adys.wh@gmail.com
orm=fbo In d3d mode with detailed shadows, WoW tends to crash with out of memory errors very fast. With shadows set to High, running around in Dalaran at peak time will crash in a few minutes at best.
(Reported for posterity, I'll be unavailable to test for the next few days)
http://bugs.winehq.org/show_bug.cgi?id=24826
--- Comment #1 from Austin English austinenglish@gmail.com 2010-10-20 15:14:57 CDT --- Have you tested it on windows? May be an application bug.
http://bugs.winehq.org/show_bug.cgi?id=24826
--- Comment #2 from Jerome Leclanche adys.wh@gmail.com 2010-10-20 15:16:52 CDT --- (In reply to comment #1)
Have you tested it on windows? May be an application bug.
Positive it doesn't happen on windows; it crashes in mere minutes, while on Windows I've had absolutely no crash report with shadows enabled.
http://bugs.winehq.org/show_bug.cgi?id=24826
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|WoW 4.x D3D: Out of Memory |WoW 4.x D3D: Out of Memory |errors with detailed |errors after long session |shadows |
http://bugs.winehq.org/show_bug.cgi?id=24826
--- Comment #3 from Jerome Leclanche adys.wh@gmail.com 2010-12-06 06:30:31 CST --- After a recent commit batch, the shadows no longer accelerate the OOM crash. It still crashes with OOM in d3d after a few hours of play time (depending on where the character is and so on)
http://bugs.winehq.org/show_bug.cgi?id=24826
Nephyrin zey Nephyrin@nephyrin.net changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |Nephyrin@nephyrin.net
--- Comment #4 from Nephyrin zey Nephyrin@nephyrin.net 2010-12-08 12:28:01 CST --- Hacky workaround: Use editbin.exe from the windows SDK (or any other exe editor) to set /LARGEADDRESSAWARE on WoW.exe (use winedump to confirm). This will cause windows/wine to use large address mode for WoW, allowing up to 3GB of userspace memory. I have gotten no crashes since doing this, whereas it would repeatedly crash whenever memory hit 1.6GiB in the past. I'm sitting at 1.7GiB with no issues.
Disclaimer: Hacky. Blizzard might not approve of this, proceed at your own risk. Back up WoW.exe first.
http://bugs.winehq.org/show_bug.cgi?id=24826
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|WoW 4.x D3D: Out of Memory |WoW 4.x: Out of Memory |errors after long session |errors after long session
http://bugs.winehq.org/show_bug.cgi?id=24826
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |RESOLVED Resolution| |INVALID
--- Comment #5 from Jerome Leclanche adys.wh@gmail.com 2010-12-24 07:15:38 CST --- Closing invalid, it's a WoW issue. Under wine it happens faster, hell knows why, but I can't prove that.
http://bugs.winehq.org/show_bug.cgi?id=24826
Jerome Leclanche adys.wh@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #6 from Jerome Leclanche adys.wh@gmail.com 2010-12-24 07:15:58 CST --- Closing.
http://bugs.winehq.org/show_bug.cgi?id=24826
Austin English austinenglish@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |error@ioerror.us
--- Comment #7 from Austin English austinenglish@gmail.com 2011-01-08 13:21:32 CST --- *** Bug 25707 has been marked as a duplicate of this bug. ***
http://bugs.winehq.org/show_bug.cgi?id=24826
Trygve Vea trygve.vea@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |trygve.vea@gmail.com
--- Comment #8 from Trygve Vea trygve.vea@gmail.com 2011-01-08 14:03:37 CST --- How does one prove that this is an application problem vs. a bug in wine?
I want to argue that this bug should be reopened, as it's easy to reproduce it in wine - but hard to reproduce it in windows (if the bug actually occurs in windows at all).
http://bugs.winehq.org/show_bug.cgi?id=24826
--- Comment #9 from Jerome Leclanche adys.wh@gmail.com 2011-01-08 14:22:44 CST --- (In reply to comment #8)
How does one prove that this is an application problem vs. a bug in wine?
I want to argue that this bug should be reopened, as it's easy to reproduce it in wine - but hard to reproduce it in windows (if the bug actually occurs in windows at all).
The bug is easy to reproduce on Windows, however it doesn't affect every setup; you can browse the official forums for this. It's possible that the bug would be less frequent on Wine64 but WoW doesn't run on it yet.
http://bugs.winehq.org/show_bug.cgi?id=24826
--- Comment #10 from Michael Hampton error@ioerror.us 2011-01-08 16:24:27 CST --- Since someone was nice enough to mention this issue had been discussed on the Blizzard forums, I have decided to do the research and locate these forum threads.
(Remember to skip over the obvious trolls, of which there are many.)
1. Links to a standalone utility which will set the LARGEADDRESSAWARE flag, so you don't have to install the whole Windows SDK. This app seems to run OK in Wine. http://us.battle.net/wow/en/forum/topic/1118362581#18 http://www.ntcore.com/4gb_patch.php
2. Provides longer explanation of the issue and a link to a second standalone utility which will set the LARGEADDRESSAWARE flag. This app requires .NET 3.5 so probably won't work very well or at all in Wine. http://us.battle.net/wow/en/forum/topic/1670096715#10
3. Official Blizzard post stating that using LARGEADDRESSAWARE will not get you banned, and providing some other workarounds. http://us.battle.net/wow/en/forum/topic/1658706617?page=6#101
There are other threads, but these were the most useful I found.
http://bugs.winehq.org/show_bug.cgi?id=24826
jonathan@smalls.cc changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |jonathan@smalls.cc
--- Comment #11 from jonathan@smalls.cc 2012-11-09 16:36:06 CST --- I want to add support to these complaints of a memory leak after a long run. I run MetaTrader 4.x as a server process, and notice that Wine consumes progressively more memory until the server is tapped out.
-
wine-bugs＠winehq.org