Is this bad? Created 18 years ago2006-01-13 22:45:55 UTC by Guinea Pirate

I saw this message while compiling:

Memory leak: mempool blocks left in memory: 48
Memory leak: mempool blocks left in memory: 2

Is that bad? I know memory leaks are not a good thing, however the map did compile successfully.

This isn't an error. Everyone get's 'em, you can safely ignore it.

One of the Valve team members who coded it made an error in the code but luckily it doesn't cause anything bad...

I think it's more likely just an "acceptable problem" caused by the way the compile tools work.

won`t that over time fill uyp the memery till you restart your comp

I doubt it; Windows or the tools should free up all the memory the tools used.

No, the very definition of a memory leak is memory lost by the appication. And I really wouldn't expect windows to be able to clean it up.

I thought it just just continuous pointless memory allocation? Surely Windows knows what areas of memory have been asssigned to which processes.

I would never trust windows to keep track of the appications memory resources. Ever wonder why the machine gets sick after several days of running, this is why.

Xp was a huge leap in the way to fixing this, but they still got a ways to go.

The mempool area is a stability indicator, not an error. Ignore it, it's unimportant.