Hi Gonzalo,
I've investigated on my "deadlock" problem. It seems that this problem comes from GAMIN.
I explain:
I'm running a big (more than 50 aspx, ascx) web application. If I run a precompilation page (see the attached aspx.cs)
Mono, will compile about 20 pages, and will lock forever...
I
Le mardi 25 avril 2006 à 18:03 -0700, Gonzalo Paniagua Javier a écrit :
On Tue, 2006-04-25 at 18:25 +0200, Hubert FONGARNAND wrote:
> Hi Gonzalo,
>
> It seems that i've another deadlock problem,
> but it's very hard to reproduce exactly
> I've send a SIGQUIT to mod_mono_server to do a thread
On Tue, 2006-04-25 at 18:25 +0200, Hubert FONGARNAND wrote:
> Hi Gonzalo,
>
> It seems that i've another deadlock problem,
> but it's very hard to reproduce exactly
> I've send a SIGQUIT to mod_mono_server to do a thread dump :
Can you provide more data here? Specifically, the @Page or @Control
d
Hi Gonzalo,
It seems that i've another deadlock problem,
but it's very hard to reproduce exactly
I've send a SIGQUIT to mod_mono_server to do a thread dump :
- Full thread dump:
-
- "" tid=0x0xb6ca0bb0 this=0x0x152f00:
- in (wrapper managed-to-native) System.Threading.WaitHandle:Wai
On Thu, 2006-04-20 at 18:46 +0200, Hubert FONGARNAND wrote:
> Hi Gonzalo
>
> I've just highlight an important deadlock problem in ASP.NET on mono
> Please take on look on :
> http://bugzilla.ximian.com/show_bug.cgi?id=78149
I think it's already fixed. Please retest and follow up in bugzilla.
Than
Hi Gonzalo
I've just highlight an important deadlock problem in ASP.NET on mono
Please take on look on :
http://bugzilla.ximian.com/show_bug.cgi?id=78149
Thanks!
--
Hubert FONGARNAND <[EMAIL PROTECTED]>
Fiducial
___Ce message et les éventuels
