Jamba crashing game

[Lyonheart]

Im getting this >>> This application has encountered a critical error:Not enough storage is available to process this command.Program: D:\WoWd\WoW.exeFile: .\MapMem.cppLine: 558Requested 1571260 bytes of memory

I have turned off every addon and turned them on one by one.. i only get that error when i turn on Jamba. The forums suggest deleting my cache.. wtf... etc.. I'm wondering if there is another fix.. just deleting jamba and reinstalling for example? I really don't want to have to reset EVERYTHING after deleting wtf and cache hehe

[Noids]

No assistance unfortunately, but I am also getting a similar error. Wasn't sure whether it was Jamba or to do with Isboxers WTF virtualisation? I have not updated anything recently except ISboxer to build 36 a few days ago and the patch just today. Strangely enough it is only happening on my lead toon...

Any help from Jafula or Lax would be greatly appreciated.

Cheers

PS: My error is at File: D:\buildserver\wow\5\work\wow-code\branches\wow-patch-3_3_5-bnet\engine\source\blizzardcore\blizzardcore\sourc e\system\memory\MemoryStorm.cpp Line:64 Requested 9167144 bytes of memory

Out of interest, my main program is run from C drive which are my raided SSds, whereas d: is my storage raid 1 setup. Could this be a cause of relatively poor performance for me in Dal?

[Lax]

The error is probably unrelated to either Jamba or ISBoxer. The only reason this type of error should ever come up is if you're out of RAM, hence the message about requesting x amount of memory. So.. how's your RAM usage?

"Poor performance in Dalaran" could mean multiple things. If you're referring to generally low FPS (standing still), it's probably more related to maxing CPU and GPU. If you're referring to stutters when the game loads new resources (e.g. because a new player comes into range, from loading building textures, etc) but then general FPS is fine (standing still), this would be affected by your hard drives (SSDs).

[Noids]

RAM usage for me sits at around 25-30% of my 12GB normally. This is a completely new problem for me today after patching.

The performance in Dal and in general I was referring to is simply lower than expected fps (in the 20s generally) for an i920, 12GB GTX 295 SSD type system. I had purchased the SSDs to be used for WoW primarily and installed the game on them so was surprised to see in the error that a file on my D drive was the one requesting the memory allocation. Even more surprising is that I do not have a directory on my D drive named D:\buildserver which is whatled me to question the WTF virtualisation of Innerspace. I am an experienced computer user but have no experience with any sort of software programming etc. so I am assuming there is a logical explanation for this. I don't really know where to look further for this problem without being able to physically find the error in question though and was hoping you guys could shed some light on what was setting up files on a disk other than the one on which my WoW folder and addons sits.

Edit: Trying to replicate the error now. Haven't managed to as yet but started my 5 man team, all logged in fine to Dalaran, RAM at 48%. PiP switch back to my main frmo my 5th toon logged in and very slow switch, screen switches to the main section but remains at its small size in the top left corner and it is locked up but won't crash this time. Mem useage slowly climbs to 55% and plateaus at this. Started task manager and have 5 instances of WoW running. 4 of them are using about 600k but one is up to 1.2MB. This process is my window 1 which is playing up.

[Lax]

The error isn't a file on your D drive. Rather, it's indicating one of World of Warcraft's source code files. Any time a WoW crash box comes up it's going to provide debugging information to help the WoW developers identify the cause. So "D:\buildserver\wow\5\work\wow-code\branches\wow-patch-3_3_5-bnet\engine\source\blizzardcore\blizzardcore\sourc e\system\memory\MemoryStorm.cpp" is just the path and filename of one of the source code files, on the computer they use to generate official WoW client builds -- the filename is hardcoded (automatically) right into WoW.exe or related files when they build it.

If you're not out of RAM, this error is probably due to memory corruption. It's probably due to some changes they made to the code in the 3.3.5 patch (which is why it would happen now and not the day before the patch). There's no way for you or I to determine what the cause is.

A quick google for wow 3.3.5 memory error turns up some threads on the official WoW forums:
Technical Support forum, thread started by a Blizzard poster: http://forums.worldofwarcraft.com/th...sid=1&pageNo=1
A workaround might be here according to someone: http://forums.worldofwarcraft.com/th...sid=1&pageNo=1
A thread on the EU forums: http://forums.wow-europe.com/thread....46567792&sid=1

... so yeah I don't think this is in any way related to Jamba or ISBoxer

[Noids]

Cheers Lax. Have been combing the official forums also and found a few mentions of issues, but thanks for the reassurance that its unlikely to be an addon/multibox related issue :P

Hopefully you don't have to delete your WTF at this stage also Lyonheart

[Lyonheart]

i have 12gigs of ddr3. 1gig on my video card. I only crash with this error when i turn on Jamba. SO are my jamba files corrupt?

Before the patch i could run 5-6 WoWs at high settings and never crash. Now If i turn on Jamba, i crash even on low settings.

[Noids]

i have 12gigs of ddr3. 1gig on my video card. I only crash with this error when i turn on Jamba. SO are my jamba files corrupt?

Before the patch i could run 5-6 WoWs at high settings and never crash. Now If i turn on Jamba, i crash even on low settings.

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...

[Noids]

Sorry for the adjacent replies, but just thought I would update this for others affected also. I have worked around the problem as suggested by the official forum posts by turning my graphics settings to minimum and seem to get fairly stable connection for up to a couple of hours before crashing now. It seems that having my 5 set to run on a 2560x1600 monitor is partially contributing to the issue however due to the memory requirements for the resolution, so I would guess this is less likely to be affecting people with fewer addons, lower graphics settings or 1920X1200 or less monitors. No update as yet or even confirmation as to whether this is a true memory leak issue however and I find it pretty annoying that despite having a high end system in order to play at high settings, the .exe itself can not manage this...

[Jafula]

Addons _can_ crash WoW. But usually not like this. In your case I would do a complete wipe of wtf/cache/interface-addons and start over.

I've not heard of others having issues (yet)...