AppDomain.ProcessExit is not guaranteed to be called

re: AppDomain.ProcessExit is not guaranteed to be called

Mike Stall - MSFT — Fri, 29 Dec 2006 19:28:07 GMT

Sam -

I looked at the english (en-us) version of the URL instead of (zh-tw).

http://msdn2.microsoft.com/en-us/library/system.appdomain.processexit(VS.80).aspx

I see it says:

The total execution time of all ProcessExit event handlers is limited, just as the total execution time of all finalizers is limited at process shutdown. The default is three seconds, which can be overridden by an unmanaged host.

Key sentence there is "which can be overridden by an unmanaged host", which means using the hosting API (defined in mscoree.idl).

I'm not sure which hosting API. However, do you really want to rely on the ProcessExit event since it's not reliably called?

re: AppDomain.ProcessExit is not guaranteed to be called

sam — Fri, 29 Dec 2006 06:42:40 GMT

I got another problem on AppDomain.ProcessExit.

According to msdn,there is only 3 sec limit when ProcessExit.

ref url>>http://msdn2.microsoft.com/zh-tw/library/system.appdomain.processexit(VS.80).aspx

How can we extend the time limit to more than 3 sec?

thx

sam

re: AppDomain.ProcessExit is not guaranteed to be called

Mike Stall - MSFT — Fri, 01 Dec 2006 21:14:24 GMT

Antosha - you're toally right. A silly mistake on my part. I've corrected it and reverified. Thanks.

re: AppDomain.ProcessExit is not guaranteed to be called

Antosha — Fri, 01 Dec 2006 12:26:07 GMT

The example is not just contrived; it actually does not prove your point. If you kill the process on Console.ReadLine, the CurrentDomain.ProcessExit is not set *yet*.

re: AppDomain.ProcessExit is not guaranteed to be called

Mike Stall - MSFT — Mon, 27 Nov 2006 19:07:32 GMT

Anders - You're right that my example is contrived. It's trying to illustrate the limitations of ProcessExit, not find the most efficient way to call Console.WriteLine. Putting the callback at the start would be more natural.

Alois - thanks for the link.

re: AppDomain.ProcessExit is not guaranteed to be called

Alois Kraus — Mon, 27 Nov 2006 17:36:57 GMT

Hi Mike,

more infos about abnormal and cooperatice application shutdown with the CLR can be found here:

http://geekswithblogs.net/akraus1/archive/2006/10/30/95435.aspx

Yours,

Alois Kraus

re: AppDomain.ProcessExit is not guaranteed to be called

Anders Dalvander — Mon, 27 Nov 2006 14:18:05 GMT

Shouldn't the Main method be something like this instead:

static void Main(string[] args)

{

AppDomain.CurrentDomain.ProcessExit += new EventHandler(CurrentDomain_ProcessExit);

Console.WriteLine("start");

Console.ReadLine();

}

It still doesn't help against kernel32!TerminateProcess, but placing the code at the end of the Main method seems like a strange and cumbersome way to call Console.WriteLine indirectly.