I'm currently trying to use nedmalloc v1.05 to increase performance. The performance indeed increased, but memory usage rised from more than 300MB to over 800MB, and still continued increasing!!

Help!! Let's stop this beast!!

Are you sure that you are correctly deallocating memory? Have you read Question #3 in the FAQ? How are you measuring memory usage?

I don't know anything about your application, so I can only assume you are making some mistake in freeing the memory or in measuring what memory is being used.

Are you sure that you are correctly deallocating memory? Have you read Question #3 in the FAQ? How are you measuring memory usage?

I don't know anything about your application, so I can only assume you are making some mistake in freeing the memory or in measuring what memory is being used.

Our application is an online action game. I use Windows 7 TaskManager to measure memory usage.

Task manager should not be used to measure the resource usage of an application. Even if you free memory, task-manager might not reflect this.

How many threads are you making allocations from?

What sized allocations are you making?

What tools and procedures have you used to ensure you don't have any memory leaks?

Task manager should not be used to measure the resource usage of an application. Even if you free memory, task-manager might not reflect this.

How many threads are you making allocations from?

What sized allocations are you making?

What tools and procedures have you used to ensure you don't have any memory leaks?

We override operator new and delete to adopt nedmalloc. I know that TaskManager may be not accurate, but the read memory increased to more than double, I think that it's not normal.

We don't create any threads ourselves. But some 3rd party codes create threads themselves, like network, sound, and so on. Some codes are linked in through static libs, so I think that they may use nedmalloc, because I override new and delete.

Memory leaks actually exists, but just a little. We use _CrtSetDbgFlag() to report memory information in debug.

Well, it seams not a good idea and dangerous to overrde default new and delete to manage memory.

Now I'm trying to replace only needed part with nedalloc, and it's currently OK .