I thought it was funny too, but it's my recollection that, in a rare
moment of Slashdot insightfulness, the early comments mostly were of
the "RTFA" type, pointing out how the referenced blog entry isn't about
a bug in C# or .NET at all, but rather just an ad for a profiling tool
to help a developer find their _own_ bugs.

In fact, I was a little surprised at the general lack of anti-MS
sentiment.  Granted, I only read the first dozen or so comments; it
wouldn't surprise me to find that the comments eventually degenerated
into the usual Microsoft bashing.

Pete

When you get to the article itself we find that this is a very old and common
problem (the cause of which is what is between the computer and the chair):

"We profiled the memory usage and saw the obstacle list blowing up. How
could this be? We called "delete" on those old obstacles! To our amazement,
it was only minutes before we realized that our list of detected obstacles
was never getting garbage collected. Though we thought we had cleared all
references to old entries in the list, because the objects were still
registered as subscribers to an event, they were never getting deleted."

----Peter
"Inside every large program, there is a small program trying to get out."
http://www.eggheadcafe.com
http://petesbloggerama.blogspot.com
http://www.blogmetafinder.com