Re: Memory Leak still in my app

[Joseph Bruni]

Can you run your server for thousands of iterations to see if the memory continues to be consumed? Generally memory that has been allocated by the C library is not returned to the OS. Instead those pages are cached to handle future allocations without needing to request them from the OS.

If your program continues to burn memory after thousands of iterations, you probably have a memory leak. Otherwise if it levels off it's probably just being cached.

On Aug 31, 2004, at 5:53 PM, Carlos Roberto Zainos H wrote:

So, I don't understand why after 100 consecutive connections the memory grows up 4.5 Kb .... something is not being freed, (bios are not problem) how can I see if the structures are freed?? (points to NULL)

smime.p7s
Description: S/MIME cryptographic signature