[Mono-bugs] [Bug 72637][Wis] Changed - [RACE?] DeleteCriticalSection assertion failed error

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 24 Feb 2005 09:58:36 -0500 (EST)


Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by vguzev@yandex.ru.

http://bugzilla.ximian.com/show_bug.cgi?id=72637

--- shadow/72637	2005-02-16 13:07:54.000000000 -0500
+++ shadow/72637.tmp.5600	2005-02-24 09:58:36.000000000 -0500
@@ -135,6 +135,48 @@
 
 ------- Additional Comments From dick@ximian.com  2005-02-16 13:07 -------
 The assert in critical-sections.c is showing that someone has a
 mismatch between EnterCriticalSection and LeaveCriticalSection
 
 
+
+------- Additional Comments From vguzev@yandex.ru  2005-02-24 09:58 -------
+OK, Here's another one sample (attached).
+It starts 1000 threads, that're trying to call 
+System.Environment.Exit at a given time (in the nearest 10 seconds).
+
+When I try to run it on Mono 1.1.4 I get the following errors:
+--8<-------------------------------------------
+[vadim@skif testsimultaneousexit]$ mono test.exe
+Current date: 02/24/2005 16:44:45
+Stopping after: 02/24/2005 16:44:50
+Stopped..
+Stopped..
+
+(test.exe:24250): GLib-CRITICAL **: file ghash.c: line 225 
+(g_hash_table_lookup): assertion `hash_table != NULL' failed
+
+(test.exe:24250): GLib-CRITICAL **: file ghash.c: line 225 
+(g_hash_table_lookup): assertion `hash_table != NULL' failed
+
+(test.exe:24250): GLib-CRITICAL **: file ghash.c: line 225 
+(g_hash_table_lookup): assertion `hash_table != NULL' failed
+
+(test.exe:24250): GLib-CRITICAL **: file ghash.c: line 225 
+(g_hash_table_lookup): assertion `hash_table != NULL' failed
+
+** ERROR **: file mempool.c: line 144 (mono_mempool_alloc): 
+assertion failed: (pool != NULL)
+aborting...
+Aborted
+--8<-------------------------------------------
+
+Sometimes it works as expected.
+What's interesting, that if I try remove line 'Console.WriteLine
+( "Stopped.." );' then the program just hangs on without any errors 
+and doesn't exit at all...
+
+
+Best regards,
+Vadim B. Guzev
+http://u.pereslavl.ru/~vadim/MCSharp/
+