The way I read the issue as reported on the WoW forums is that anything that increases memory utilisation will cause your instances to crash more quickly. So whilst Jamba is not directly responsible for the crash, it is adding to the memory used by WoW. Other things that increase the memory utilisation are higher graphics settings, viewing distances, more populated areas etc. The issue is that your WoW instance hits it's maximum memory allocation rather than your total maximum memory which I assume would crash your complete OS instead. I have also read that it is more common with 64 bit systems although it does occur on 32 bit systems also. I assume this is because 64bit systems require more memory to run the same program? (I'm sure others can explain this better).
The posted fix is not legal according to Blizz as it is an altered Wow.exe file which allows for an extra 50% memory allocation per instance. The devs are apparently working on a fix and I assume there will be an emergency patch in the next few days...
Connect With Us