Don't forget that garbage collection makes memory available for re-use by the program, but does not (generally) release memory to the operating system.
Releasing memory to the OS is a complicated matter that most applications/languages/frameworks do not attempt, and is not possible on many OSes.
In any case, if you have a long-running program that uses and releases memory objects, it would be a pointless expense to release memory to the OS, since you will later allocate new objects, which requires requesting more memory. Only in the case of requiring large amounts of memory during an early stage, followed by a lengthy low-memory-requirement phase, would it make sense. I suppose in such a case you could fork a separate process with the heavy memory requirements, so that it will terminate and release memory, after sending the required data to the main process.
--
TTTATCGGTCGTTATATAGATGTTTGCA
In reply to Re: Gregorian Garbage Collection...
by TomDLux
in thread Gregorian Garbage Collection...
by edwar64896
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |