Check out the CLR Lead Architect's New Blog

New and Notable 127

Sam Gentile's Blog — Wed, 03 Dec 2008 21:20:38 GMT

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

re: Check out the CLR Lead Architect's New Blog

markovich — Sat, 06 Oct 2007 23:55:34 GMT

Is this the expected behaviour or a non conformity?

re: Check out the CLR Lead Architect's New Blog

Maoni Stephens — Tue, 28 Nov 2006 02:41:15 GMT

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.

re: Check out the CLR Lead Architect's New Blog

Alois Kraus — Fri, 24 Nov 2006 11:34:38 GMT

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

New and Notable 127

Sam Gentile — Thu, 23 Nov 2006 18:11:52 GMT

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