Check out the CLR Lead Architect’s New Blog


Many people know Patrick Dussud by his outstanding work on Garbage Collection. But did you know he was one of the founders of the CLR? In his intro blog entry he talks about how the CLR came to life. I am sure it will be a great read for those of you who are curious about it.

Comments (7)

  1. Sam Gentile says:

    I thought Thanksgiving morning is for adults to be sleeping in. Instead, not only are the kids up at

  2. Alois Kraus says:

    Hi,

    I was just wondering why the garbage collector does stop finalizing when you take a lock inside a finlizer which you do not own.

    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=954304&SiteID=1

    Is this the expected behaviour or a non conformity?

    Could you elaborate a bit the cooperation of the GC and locks inside finalizers?

    Yours,

     Alois Kraus

  3. Alois, first of all it’s not GC that "does stop finalizing" – GC doesn’t run finalizers, it just tells the finalizer thread if there are finalizers to run and the finalizer thread runs them. It’s up to the runtime policy to decide whether to abort the finalizers or wait infinite. Currently the runtime policy is to wait infinitely for finalizers during appdomain unload and wait for certain number of seconds total during process shutdown (and for each finalizer there’s also a timeout value).

    You can change the timeout for AD unload and shutdown via hosting interface ICLRPolicyManager.

  4. markovich says:

    Is this the expected behaviour or a non conformity?

  5. I thought Thanksgiving morning is for adults to be sleeping in. Instead, not only are the kids up at the crack at dawn but one (the eight year old) is playing games on Vista and asking for Starbucks, while the nearly 4 year old is clamoring for princess

  6. Sami Suliman says:

    How does that goes? http://www.tateberry.com

  7. Home Extension Centre says:

    Is this the expected behavior or a non conformity? I think it's both. http://www.homeextensioncentre.co.uk