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.

Sursa
2007-07-14 20:03:00



Comenteaza





Ultimele 25 posturi adăugate

19:45:36Vrea să candideze independent la ambele funcții elective din sat —» Curaj.TV | Media alternativă
12:01:50Impresii de la Clubul de lectură „Tainele cărții” —» Biblioteca de Arte 'Tudor Arghezi'
04:58:47Poezia cu rădăcinile în inima cititorului! —» BiblioCity
20:44:32#MasaCritica #București, septembrie 2023 —» Curaj.TV | Media alternativă
20:41:30Junglă de ambrozie pe malul lacului Cernica —» Curaj.TV | Media alternativă
20:38:29Jandarmii încercau să ne împingă de pe alee —» Curaj.TV | Media alternativă
20:34:57Poluare cu nisip pe trotuar la Pallady —» Curaj.TV | Media alternativă
22:54:55Queer Québec and Feminist Studies —» turn up the silence
20:46:07Oleg Brega la Jurnalul unei emigrante —» Curaj.TV | Media alternativă
15:48:51Niște inși agresivi au chemat poliția pentru că mîncam în parc —» Curaj.TV | Media alternativă
15:40:46Poliția locală a oprit drujbele de Călărași care tăiau în IOR —» Curaj.TV | Media alternativă
18:48:33Even More New WordPress.com Themes for September 2023 —» Ileana Pîrgaru
14:50:04Aroganța polițienească e contagioasă —» Curaj.TV | Media alternativă
11:40:07Adio, Ion Druță! —» Argentina Gribincea's Blog
09:13:57O VIZITĂ LA ION DRUȚĂ. MOSCOVA —» Leo Butnaru
17:43:25Protest feminist la Ministerul Sănătății – Avortul e un drept! —» Curaj.TV | Media alternativă
13:40:36LOCUL DE VECI AL LUI ION DRUȚĂ —» Leo Butnaru
13:21:26Simpozionul National de Studii Culturale, ediția a V-a —» Biblioteca de Arte 'Tudor Arghezi'
09:41:42ION DRUȚĂ: 3.IX.1928 - 28.IX.2023 —» Leo Butnaru
18:13:08Influence the Future of WordPress by Taking the 2023 Annual Survey Today —» Misterioz
15:58:32Cică primarul neagă că hrănește muncitorii la grădiniță —» Curaj.TV | Media alternativă
07:00:49Veniţi la Mine, toţi cei trudiţi și împovăraţi, și Eu vă voi da odihnă —» Moldova Creștină
04:52:46Despre ultima ședință a consiliului local Burlacu —» Curaj.TV | Media alternativă
18:17:07Seminar raional cu profesorii de educație pentru societate —» Centrul Comunitar Instruire, Acces Informaţie Călăraşi
13:50:47Supărat că poliția de la Edineț nu-și face datoria —» Curaj.TV | Media alternativă