It sounds kind of like Microsoft file detete, where they set a flag on the file
making it available for overwrite, but not physically clearing the memory and making
it immediately available again.
It would be interesting to examine the garbage collection process, and see what's actually
being done. I suspect that with proper precautions, there would be a way to 'pop' the memory
allocation completely off the allocation stack.
making it available for overwrite, but not physically clearing the memory and making
it immediately available again.
It would be interesting to examine the garbage collection process, and see what's actually
being done. I suspect that with proper precautions, there would be a way to 'pop' the memory
allocation completely off the allocation stack.