DotNetKicks.com - Stories tagged with GC

How the Garbage Collector works - Part 2

Sat, 03 May 2008 14:46:56 GMT

Now let's go deeper to understand how the Garbage Collector (GC) is actually collecting the dead objects and how this may affect the performance.

How the Garbage Collector works - Part 1

Sat, 03 May 2008 11:37:35 GMT

The Garbage Collector (GC) can be considered the heart of the .NET Framework. It manages the allocation and release of memory for any .NET application. In order to create good .NET applications, we must know how the Garbage Collector (GC) works.

Things you MUST dispose

Wed, 02 Apr 2008 08:46:02 GMT

When the .NET Framework instantiates an object, it allocates memory for that object on the managed heap. The object remains on the heap until it's no longer referenced by any active code, at which point the memory it's using is reclamed by the Garbage Collector (GC). Before the GC deallocates the memory, the framework calls the object's Finalize() method, but developers are responsible for calling the Dispose() method.

A good reason for calling GC.Collect()

Mon, 24 Sep 2007 14:46:01 GMT

Using GC.Collect to verify object destruction in unit tests.

Top 20 .Net GC Articles

Sat, 23 Jun 2007 09:03:54 GMT

Top 20 .Net GC Articles

Top 20 .NET Garbage Collection Articles

Sat, 23 Jun 2007 00:31:01 GMT

Ah. Garbage Collection... how I love and hate thee. =P I think one sad thing about programming in .net is that it seems many developers don't know or care anything about garbage collection and memory management. You used to *have* to know about it in order to write bug free code. I suppose it is a two edge sword in that developers can develop faster as the intention was to relieve developers of the need to know or care anything about memory management. I personally have always tried to follow best practices for implementation and have tried to stay somewhat cautious of issues related to memory. I've been fortunate in never really having any memory management related issues in my previous applications. However, there, but for the grace of God, I too could go.

Managing unmanaged memory

Tue, 15 May 2007 07:00:34 GMT

The title of this post might seem confusing. Garbage Collector (or GC) in .Net is designed to take care of managed memory only, so what do you do in a case where you have a managed object that itself takes very small amount of memory but allocates significant amount of unmanaged resources? In that case....

How to Use the Singleton Pattern and the Garbage Collector to Manage a

Mon, 14 May 2007 03:31:01 GMT

Here's an easy to minimize the overhead of an expensive resource, such as an image or a network connection, using the singleton pattern and some simple hints to the garbage collector.

Did it with .NET - Adventures with the Garbage Collector and the JIT O

Tue, 24 Apr 2007 17:58:03 GMT

Dan Shechter's code sample that illustrates a certain peculiarity of the .NET garbage collector.

Adventures with the Garbage Collector and the JIT Optimizer

Wed, 18 Apr 2007 10:32:22 GMT

This article delves into a certain peculiarity of the .NET garbage collector. Along the way, it explores IL, optimized JIT-compiled code and even the underlying CLR structures.

Adventures with the Garbage Collector and the JIT Optimizer

Wed, 18 Apr 2007 10:32:22 GMT

This article delves into a certain peculiarity of the .NET garbage collector. Along the way, it explores IL, optimized JIT-compiled code and even the underlying CLR structures.

A quiz about the .net garbage-collector

Thu, 19 Apr 2007 08:01:01 GMT

Tess lists some "potential interview questions" about the .net GC. He lists the answers in a followup post: http://blogs.msdn.com/tess/archive/2007/04/10/net-garbage-collector-popquiz-followup.aspx