Garbage collection

The garbage collector is .NET’s answer to memory management, and in particular to the question of what
to do about reclaiming memory that running applications ask for. Up until now there have been two
techniques used on the Windows platform for de-allocating memory that processes have dynamically
requested from the system:
❑ Make the application code do it all manually.
❑ Make objects maintain reference counts.
Having the application code responsible for de-allocating memory is the technique used by lower-level,
high-performance languages such as C++. It is efficient, and it has the advantage that (in general)
resources are never occupied for longer than unnecessary. The big disadvantage, however, is the frequency
of bugs. Code that requests memory also should explicitly inform the system when it no longer
requires that memory. However, it is easy to overlook this, resulting in memory leaks.
Although modern developer environments do provide tools to assist in detecting memory leaks, they
remain difficult bugs to track down, because they have no effect until so much memory has been leaked
that Windows refuses to grant any more to the process. By this point, the entire computer may have
appreciably slowed down due to the memory demands being made on it.
Maintaining reference counts is favored in COM. The idea is that each COM component maintains a
count of how many clients are currently maintaining references to it. When this count falls to zero, the
component can destroy itself and free up associated memory and resources. The problem with this is
that it still relies on the good behavior of clients to notify the component that they have finished with it.
It only takes one client not to do so, and the object sits in memory. In some ways, this is a potentially
more serious problem than a simple C++-style memory leak, because the COM object may exist in its
own process, which means that it will never be removed by the system (at least with C++ memory leaks,
the system can reclaim all memory when the process terminates).
The .NET runtime relies on the garbage collector instead. This is a program whose purpose is to clean up
memory. The idea is that all dynamically requested memory is allocated on the heap (that is true for all
languages, although in the case of .NET, the CLR maintains its own managed heap for .NET applications
to use). Every so often, when .NET detects that the managed heap for a given process is becoming full
and therefore needs tidying up, it calls the garbage collector. The garbage collector runs through variables
currently in scope in your code, examining references to objects stored on the heap to identify
which ones are accessible from your code—that is to say which objects have references that refer to
them. Any objects that are not referred to are deemed to be no longer accessible from your code and can
therefore be removed. Java uses a similar system of garbage collection to this.
Garbage collection works in .NET because IL has been designed to facilitate the process. The principle
requires that you cannot get references to existing objects other than by copying existing references and
that IL is type safe. In this context, what we mean is that if any reference to an object exists, then there is
sufficient information in the reference to exactly determine the type of the object.
It would not be possible to use the garbage collection mechanism with a language such as unmanaged
C++, for example, because C++ allows pointers to be freely cast between types.

One important aspect of garbage collection is that it is not deterministic. In other words, you cannot
guarantee when the garbage collector will be called; it will be called when the CLR decides that it is
needed (unless you explicitly call the collector). Though it is also possible to override this process and
call up the garbage collector in your code.

2007-07-14 20:03:00


Ultimele 25 posturi adăugate

05:14:05ECOU DE LA PONT —» Leo Butnaru
19:34:07James Rickards – Sold Out —» APort | "Pentru un român care știe citi, cel mai greu lucru e să nu scrie." I.L. Carag
09:57:53Fericirea stă în lucruri mici! —» Sunt MAMĂ!
09:52:13Micile și marile bucurii ale lunii martie-aprilie 2024 —» Sunt MAMĂ!
21:41:02Ce cărţi bune am mai citit (17) —» APort | "Pentru un român care știe citi, cel mai greu lucru e să nu scrie." I.L. Carag
15:05:25DIN VITRALIU # 60 (IV) —» Leo Butnaru
05:29:37POEME DIN „MIȘCAREA LITERARĂ” —» Leo Butnaru
19:36:37Râde cel care râde la urmă. Veronica Dragalin pare hotărâtă să lupte pe bune cu corupția, cu sau fără sediu propriu —» Nicolae Federiuc
09:19:40Școala de vară cu pregătire olimpică la fizică 2024 —» Fizica pentru Moldova
05:29:36DIN VITRALIU # 60 (III) —» Leo Butnaru
15:24:55Primarul incită la ură, rezolvă problema apei cu ușa încuiată —» Curaj.TV | Media alternativă
15:00:22Plantează și îngrijește pomi la marginea capitalei —» Curaj.TV | Media alternativă
14:45:48Șantier poluant, lăudat de poliția locală a lui Ciucu —» Curaj.TV | Media alternativă
14:43:01Pajiștea, la fel de importantă ca pădurea —» Curaj.TV | Media alternativă
13:47:34Întâlnirea bibliotecarilor – bucuria cititorilor —» BiblioCity
05:18:35Concursul literar „La izvoarele înțelepciunii” dedicat vieții și activității literare a poetului Vasile Romanciuc —» BiblioCity
05:02:48Găsiți-l și cereți-i cartea cu autograf – Vă va înfrumuseța prezentul și, mai ales, viitorul —» BiblioCity
05:01:58Răsărit literar la Biblioteca „Mihail Ciachir” —» BiblioCity
04:53:38DIN VITRALIU # 60 (Nr. 2) —» Leo Butnaru
21:46:51Vampiru’ deputat —» APort | "Pentru un român care știe citi, cel mai greu lucru e să nu scrie." I.L. Carag
19:06:25El Dorado —» Andrei LANGA. Blogul personal
15:36:13În trecere —» APort | "Pentru un român care știe citi, cel mai greu lucru e să nu scrie." I.L. Carag
13:39:35Săptămâna Inovației și Creativității 2024 —» Biblioteca de Arte 'Tudor Arghezi'