

So, we need Blizzard to acknowledge this problem and either enable large address awareness, or perform some cache trimming at these locations where they fail on virtual address space exhaustion. It's not possible to modify the WoW binary (say with editbin.exe /LARGEADDRESSAWARE) to enable this support, as some game verification performed at login time includes the PE header in its hash calculations. The WoW binary is not large address aware, so even on 64bit OSes (or systems with the /3GB boot time option) it is restricted to a 2GB userland virtual address space. The commit size + reserved size (some of the reserved ranges won't be available for heap/mmap allocations from WoW) + address space fragmentation is causing a situation where there's no place for the ~2MB attempted allocation to go, causing it to fail and producing the error above. AFAIK it's not possible to get a view of WoW's actual address space without violating the AUP/EULA, so I have not done so. Note that this isn't an exact measure of the amount of virtual address space in use by WoW, since virtual allocations can be either in a non-committed (reserved) or committed state. I've been monitoring my WoW process, particularly paying attention to the commit size column, and noticed before the crashes that it was around 1.7GB. So freeing up disk space, as suggested in several posts, is completely irrelevant to this bug. When is Blizzard gone make a WoW64.EXE ore at least make it ''/LARGEADDRESSAWARE''Īnd all the blue post on this subject are more ore less useless as the only diminishes the problem not fixing it, and now after the bug infested 4.0.1 i cant be in Dalaran anymore when there are a lot of people there >_ string conversion within WoW). This is a problem for all players that uses +4 mega pixel display like 30" 2560 x 1600, ore even worse like me whit a 7 mega pixel Eyefinty setup 5760 x 1200 like i have.īefore 4.0.1 it was all ready bad, but after 4.0.1 patch it got real bad, crashing all the time now WoW crashes now all the time after the 4.0.1 patch Program:Ĝ:\Program Files (x86)\World of Warcraft\Wow.exeĪnd to no tanks to Blizzard, i found out my self how to fix it, and i dont even know sh*t about programing >_ Not enough storage is available to process this command. This application has encountered a critical error: If you get the following crash report saying that you run out of storage space, then here is the fix for it :D
