What is causing the "not enough storage to process this command"?

[Mathayis]

So, i've been working on this map for over 5 years now. been doing a lot of testing and all....I've recently tried playing through the entire game, about 20 hrs in.... it was working fine for the first 8 hrs until eventually when I go to start playing again, loading a saved file, I get the error saying "not enough storage to process this command"
I found resetting Warcraft 3 usually helped earlier, but it now no longer works I can no longer load a saved file, which makes my map useless "even tried restarting my computer.....

Is there any easy way to fix this? I'm not very computer smart...all I know is I have over 300 custom models in them map, a lot of them I don't use... Would deleting them help any? also, i have a tun of imported music....perhaps if i deleted some of those??

the file size of my Map is 368 MB....

Anyhow....yeah...

 

[Dr Super Good]

Are you using 1.31? If you are this must be a bug with Warcraft III save/load.

 

[Mathayis]

Are you using 1.31? If you are this must be a bug with Warcraft III save/load.

Hey thank you so much for the reply! I'm actually using 1.29. I'm kinda just hoping it's a bug in this version, and will work on an other versions maybe nxt update or something XD Sooo I guess for now I'll continue working on the map, hoping it'll work

 

[Dr Super Good]

Hey thank you so much for the reply! I'm actually using 1.29. I'm kinda just hoping it's a bug in this version, and will work on an other versions maybe nxt update or something XD Sooo I guess for now I'll continue working on the map, hoping it'll work

You are hitting the 2GB virtual memory address space limit of 32bit applications, possibly as the result of memory leaks. This became a huge problem when they migrated to using CASC since CASC uses memory mapped I/O which uses up much of the virtual memory address space. This is fixed in 1.31 since one can run Warcraft III in 64bit mode (which is large address aware) which has no practical virtual memory address limit (8TB).

Be aware of migration issues with 1.31, especially those which can cause the editor to permanently corrupt map strings. These should be fixed in 1.31.1 when that is released.