[Mono-dev] Re: DeadLock Problem in ASP.NET (GAMIN)

Robert Jordan robertj at gmx.net
Thu Apr 27 08:40:58 EDT 2006


Hubert FONGARNAND wrote:
> 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... 
> If you send a SIGQUIT to mod_mono_server you will obtain that some
> thread do :
> 
> - "" tid=0x0xb646bbb0 this=0x0x3893c0:
>   - in (wrapper managed-to-native)
> System.IO.FAMWatcher:gamin_MonitorDirectory
> (System.IO.FAMConnection&,string,System.IO.FAMRequest&,intptr) <0x4>
> - in (wrapper managed-to-native)
> System.IO.FAMWatcher:gamin_MonitorDirectory
> (System.IO.FAMConnection&,string,System.IO.FAMRequest&,intptr)
> <0xffffffbf>
>   - in System.IO.FAMWatcher:FAMMonitorDirectory
> (System.IO.FAMConnection&,string,System.IO.FAMRequest&,intptr) <0x1f>
>   - in System.IO.FAMWatcher:StartMonitoringDirectory
> (System.IO.FAMData,bool) <0x7d>
>   - in System.IO.FAMWatcher:StartDispatching
> (System.IO.FileSystemWatcher) <0x192>
>   - in System.IO.FileSystemWatcher:Start () <0x17>
>   - in System.IO.FileSystemWatcher:set_EnableRaisingEvents (bool) <0x27>
>   - in (wrapper remoting-invoke-with-check)
> System.IO.FileSystemWatcher:set_EnableRaisingEvents (bool) <0xffba2006>
> 
> So the gamin_MonitorDirectory will never end and block all the other
> thread...
> The only way to force compilation contunation is to kill gam_server...
> The compilation will continue, compile 5 page, and will block again!!
> 
> I've tried to remove gamin from my linux...
> and suprise!!!
> 
> It work well, without gamin!
> 
> Is there a way to tell mono, not to use gamin, for FAMWatcher, even if
> gamin is installed?
> My version of gamin, is the last one: 0.1.7


Set the env var MONO_MANAGED_WATCHER=1

BTW, can you reproduce this one?
http://bugzilla.ximian.com/show_bug.cgi?id=78029

It's a similar (?) compilation issue that occurs even with the
default managed watcher.

Robert




More information about the Mono-devel-list mailing list