DRASTIC MEMORY OVERFLOW: Fell out of small block heap!
If this appears during compilation, should I be worried? My map appeared to compile fine. The small block heap error is supposedly because of having (you guessed it) too many small blocks, but the error appeared after I added a few point entities into the map, not any brushes. I had never seen the error before then. Ive also made maps with much more complex geometry and not got this error.
Also, no-where on the internet could I find any reference to the exact wording of this error.
So should I be concerned? It sure doesnt sound good.
I think in terms of boolean variables. Generally, it makes things easier.
I found this awesome new website that lets you type in search terms (ie; error codes) and it returns web results based on it.
PortalStories.com
"Oh, in case you got covered in that repulsion gel, here's some advice the lab boys gave me: DO NOT get covered in the repulsion gel."
Really mate? Could you send me a link to this website, because ive obviously never heard of it. I totally wouldnt have tried searching for my problem, and, in fact, tried the exact soloution you recommended. Which didnt work.
Did i also not say that i couldnt find any reference to this EXACT error?
Search for "drastic memory overflow" "fell out of small block heap" and there are only two results......the posts in this thread.
So thanks.
I think in terms of boolean variables. Generally, it makes things easier.
You didn't happen to carve to make terrain did you?
nope.
I think in terms of boolean variables. Generally, it makes things easier.
Hey Nugget
I'm having that same warning error with one of my maps as well. I'm guessing that it is related, as our sarcastic (BUT FUNNY) mate iWork said, to func_details compossed by (many) tiny brushes. I'll tell you what I've got:
1. I made a square brush size around 128x128 units (can't really remember) and made a hole in the center with a size so the elevator prop can pass through, BUT by clipping. Anyway, even though I didn't use the carve tool, this clipped brush can be compossed of around 48-56 smaller brushes currently. This is my fault because I should have stop-clipping/select-a-new-piece-of-brush/clip-again/select-a-new..... etc. I think I can reduce that number to 20 or so, I'll try this evening and post again if I manage to determine if this could be the cause and think that I can be of help to you.
2. I've grouped into 1 single func_detail many brushes with different sizes and I'm starting to think that this can cause any kind of problem when compiling... maybe making more func_details would be a better idea instead of just 1, but I have to try...
useful tools and stuff here on TWP 
[spoiler]
[/spoiler]Did i also not say that i couldnt find any reference to this EXACT error?
Search for "drastic memory overflow" "fell out of small block heap" and there are only two results......the posts in this thread.
So thanks.
I sawwwy... I searched with australian google, which provides a ton of threads. Maybe [subject hometown here]'s google isnt as good.
PortalStories.com
"Oh, in case you got covered in that repulsion gel, here's some advice the lab boys gave me: DO NOT get covered in the repulsion gel."
I know this thread is super old, but what do you do when there are NO FUNC_DETAILS and you get this error??