RE: [GD-Windows] memory leak?

[David N. <dno...@mi...>]

> [C] Lazy C runtime library is hanging on to
>   memory after all allocations are freed
>   just because it is likely you'll want
>   more memory again in the near future
>   -- and maybe it can avoid expensive
>   system calls.
>=20

STL hangs on to memory that it pools. It will reuse it later. And it
will be properly freed when the CRT shuts down (and it will be freed,
doesn't rely on the process cleanup). This was bothering as I couldn't
tell what were real leaks from STL 'leaks', however, there was a way of
either forcing the stl to free or making the leak detector work. I'll
dig up my home code tonight and post an answer.

David