|garbage collection firstname.lastname@example.org (Lex Spoon) (2003-07-13)|
|Garbage collection email@example.com (2004-07-28)|
|Re: Garbage collection firstname.lastname@example.org (2004-08-04)|
|Re: Garbage collection email@example.com (Sebastian) (2004-08-04)|
|Re: Garbage collection firstname.lastname@example.org (2004-08-05)|
|Re: Garbage collection email@example.com (Basile Starynkevitch \[news\]) (2004-08-05)|
|Re: Garbage collection firstname.lastname@example.org (Nick Roberts) (2004-08-09)|
|Re: Garbage collection email@example.com (2004-08-10)|
|Re: Garbage collection firstname.lastname@example.org (glen herrmannsfeldt) (2004-08-11)|
|Re: Garbage collection email@example.com (Nick Roberts) (2004-08-13)|
|[15 later articles]|
|Date:||4 Aug 2004 02:45:19 -0400|
|Posted-Date:||04 Aug 2004 02:45:19 EDT|
William McCabe wrote:
> I know how a copying and generational collector works but Im not sure
> how they work when put together. [snip] Can
> someone shield some light on this subject for me.
You can read the following 2-part article from MSDN. It quite nicely
explains how .Net garbage collector works -- it's also (partly*) copying &
generational collector at one (it even has 2 generations).
*) it's copying GC for not too large objects (AFAIR less than 16KB), larger
objects are allocated from yet another heap and are unmoveable (as moving
large obiects to compact memory is too slow)
"Never underestimate the power of human stupidity" -- from Notebooks of L.L.
Return to the
Search the comp.compilers archives again.