[Mono-list] Mono 2.8.1 Assertion condition `mono_wsq_count (wsq) == 0' not met

Oceanzerg oceanzerg at gmx.de
Sat Jan 15 11:13:47 EST 2011


we are currently having serious problems running a pure c# application on
mono 2.8.1 on debian 5. 

We are using .net webservices as well as async sockets and probably found a
race condition in the mono threadpool. 

I would be thankful for every idea. 

if someone has informations if mono 2.8.1 has known problems on debian 4/5
that might have something to do with this, please answer too:) 

Do you think it is a possible solution to switch to mono 2.6.7? 

Assertion at mono-wsq.c:73, condition `mono_wsq_count (wsq) == 0' not met 


Native stacktrace: 

    mono [0x48f582] 
    /lib/libpthread.so.0 [0x2abe8f8d2a80] 
    /lib/libc.so.6(gsignal+0x35) [0x2abe8fb12ed5] 
    /lib/libc.so.6(abort+0x183) [0x2abe8fb143f3] 
    mono [0x5cd042] 
    mono [0x5cd21a] 
    mono [0x5f271a] 
    mono [0x5924ca] 
    mono [0x58c24b] 
    mono [0x5bd83b] 
    mono [0x5e9ed6] 
    /lib/libpthread.so.0 [0x2abe8f8cafc7] 
    /lib/libc.so.6(clone+0x6d) [0x2abe8fbb064d] 
Debug info from gdb: 

================================================================= Got a
SIGABRT while executing native code. This usually indicates a fatal error in
the mono runtime or one of the native libraries used by your application. 
View this message in context: http://mono.1490590.n4.nabble.com/Mono-2-8-1-Assertion-condition-mono-wsq-count-wsq-0-not-met-tp3219214p3219214.html
Sent from the Mono - General mailing list archive at Nabble.com.

More information about the Mono-list mailing list