[Mono-devel-list] Re: Patch for proper cache destruction when HttpRuntime is disposed
eyala at mainsoft.com
Tue Jul 26 11:05:36 EDT 2005
Well I guess it won't change much to softly kill the timer since nobody waits until it actually
dies and if it does not die quickly enough it will be killed by the app domain unloading
I am going then to commit with the '#if TARGET_J2EE'.
On Tue, 26 Jul 2005, Gonzalo Paniagua Javier wrote:
> Date: Tue, 26 Jul 2005 10:54:08 -0400
> From: Gonzalo Paniagua Javier <gonzalo at ximian.com>
> To: Eyal Alaluf <eyala at mainsoft.com>
> Subject: Re: Patch for proper cache destruction when HttpRuntime is
> On Tue, 2005-07-26 at 17:33 +0300, Eyal Alaluf wrote:
> > Hi, Gonzalo.
> > How is the timer thread killed? In the patch the timer thread is disposed which is a soft abort
> > (no Thread.Abort called).
> > Does the AppDomain abort the threads? This can result sometimes in complex race conditions
> > that are difficult to track - this is at least the Java experience. But if in any case mant
> > threads are aborted when an app domain goes down then it doesn't change much.
> Hehe. That's exactly what's going on in the runtime. The abort sends a
> signal and waits for the code to be in a 'safe' place, but it does not
> always work. And you're right. There's has been a few races and, for
> example, assemblies are not really unloaded by now...
More information about the Mono-devel-list