Garbage Collection pain
Clemens learns a lesson about differing GC implementations. Two years ago I got all excited about GC and would spend endless hours telling anyone who would listen about the details. Today my advice is to avoid learning how it works, because it's gonna change, and you don't want to be depending on the behavior of any given collector.
...I've isolated to be a problem that I am having with .NET 1.1's garbage collector. I am doing some very, very dirty things in that particular (lab-) project, which is supposed to provide some nice, new extensibility points for Enterprise Services components. While everything was working quite well in 1.0, the updated garbage collector doesn't seem to be as forgiving as the previous one. What's ugly about provoking such bugs and heap corruption in a "concurrent GC" environment is that the application continues to run fine until the GC starts running at some point and the GC thread just tanks with a fatal error (for which I can't blame it) and tears down the whole application domain.[Clemens Vasters: Enterprise Development & Alien Abductions]
3:39:30 PM 
|
|
