memory allocation failure Created 17 years ago2007-02-21 00:39:04 UTC by cstrikefan420 cstrikefan420

Created 17 years ago2007-02-21 00:39:04 UTC by cstrikefan420 cstrikefan420

Posted 17 years ago2007-02-21 00:39:04 UTC Post #213204
this is what came up as an error file for me in the compiling process for my map
hlrad: Error: Memory allocation failure
Description: The program failled to allocate a block of memory.
Howto Fix: Likely causes are (in order of likeliness) : the partition holding the swapfile is full; swapfile size is smaller than required; memory fragmentation; heap corruption
i checked slackillers guidde and it told me to empty space for RAM and i did but it still isnt working. it happened after i added more water and a lot of aurmor entites i tried deleting some entities but it still didnt help. does any1 know the solution?
Posted 17 years ago2007-02-21 02:12:13 UTC Post #213210
Have you tried restarting the comp? If that doesn't work, scan your anti-virus and anti-spyware and see if theres anything slowing it down although i don't think thats the main thing creating that error.
Posted 17 years ago2007-02-21 09:43:54 UTC Post #213226
The entities aren't the problem in your map since it's connected to rad.(lighting) :lol: Either that you run other programs while compiling or that the map is too vast and not well optimized.
If you don't run other programs try using a batch compiler for it eats less virtual memory.(search for slackiller programs in the links page)

If thats not the problem and it's just that your map isn't well optimized here is what I think you should try to do:
I guess the water texture scale 1x1 and the water expands over a large portion of the map covering vast areas. It's simply that the compile and your computer can't cope with so much small faces. I'd seggest that you try optimizing the map as much as possible. Enlarge the water's texture scale. 2x2 might look a bit uglier, but it pays back in preformence, and it wont be so noticlible since water are usally transperant. ;)

This error is similar to the allocblock: full error, mallocblock: error...ect So if you get them it means it's still quite the same problem as the memory allocation one.
You must be logged in to post a response.