Anyone know of any online articles about the phenomenon in the subject line?
In past years, I've occasionally seen articles about it in print, but can't
seem to come up with anything via Google (yet).

"Doug Kanter" <ancientangler (AT) hotmail (DOT) com> wrote

To narrow this down a bit, I'm referring to apps which don't release all
their memory even after shutting those apps down normally (no crash).

Doug Kanter wrote:
16-bit applications generally will not clean up their DLLs if the
applications crash. This was a well-known problem with 16-bit Paradox, for
example, in relation to the IDAPI library.

32-bit applications will consistently clean-up the memory they have used, as
far as I know. I don't know about such subtleties as Windows resources and
so-on.

The "amount of RAM used" by a running Windows system may quite-normally
appear to be near-100% for prolonged periods of time, because the system
will make no effort to reallocate memory unless and until there is actual
pressure to do so. File-buffers might remain, as long as the file has not
been re-referenced by some network user or somesuch, because ..who knows,
you might need it again.


----
ChimneySweep(R): F-A-A-ST table repair at a click of the mouse!
http://www.sundialservices.com/products/chimneysweep