[Am-info] Why does NT fail to release allocated memory?

[Simon Cooke]

From: "Lewis A. Mettler" <lmettler@lamlaw.com>
>
> Is NT broken?
>
> Why is it that allocated memory is not released by NT?  I understand
> that Microsoft does not guarantee memory released by a program will be
> returned to the available pool until the program is terminated?  Or,
> does that "feature" only apply to non-Microsoft applications that do not
> use a secret API?  Or, do not identify themselves as a Microsoft
> application?
>
> Perhaps you know?

Any chance that you could be a little more specific than this? As in, give
more cases? And perhaps use a bit better grammar so that I can understand
what you're getting at here? Because at this moment in time, it sounds to me
like programmer error...

Allocated memory is generally not released by any application until you call
free() on the pointer you malloc'd, delete the object you instantiated (in
C++) or you terminate the process (which will release all memory owned by
that process).

If you could be more specific, I could help - possibly.

Simon