Thursday, 5 February 2009

Garbage collection or garbage piling up?

If you haven't tried .net or java, yet, you may want to have a look at this example of how garbage collection doesn't free your mind from thinking about memory allocation and object destruction.
at

3 comments:

  1. Anonymous5 February 2009 at 15:39

    Wow, so that's what is needed to debug a .Net app and find a leak??
    I love you .free
    I love you more AQtime

    ReplyDelete
  2. Craig5 February 2009 at 19:17

    AQTime works just fine for .NET apps. :)

    That said, the essential problem in the linked post was that the code in question used a library which was documented not to work in the situation in which it was used.... I wouldn't draw too many conclusions about MM from that.

    ReplyDelete
  3. Anonymous6 February 2009 at 15:06

    What's the point to have dispose in some objetcs and not in others.
    If I have to waste my time figuring out the must dispose objects I will end disposing every object. So, what's the point from lazyness point of view?? It's the some than .free every object

    ReplyDelete