[Mono-bugs] [Bug 81862][Maj] New - Should call g_thread_init() very early

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Tue Jun 12 04:59:15 EDT 2007

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 slomo at circular-chaos.org.


--- shadow/81862	2007-06-12 04:59:15.000000000 -0400
+++ shadow/81862.tmp.15808	2007-06-12 04:59:15.000000000 -0400
@@ -0,0 +1,36 @@
+Bug#: 81862
+Product: Mono: Runtime
+Version: 1.2
+OS Details: 
+Status: NEW   
+Priority: Major
+Component: JIT
+AssignedTo: lupus at ximian.com                            
+ReportedBy: slomo at circular-chaos.org               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: Should call g_thread_init() very early
+mono should call g_thread_init() very early on startup, otherwise (when
+called later) many glib functions might deadlock, crash or whatever if the
+application uses threads at some point. Applications can't call it in
+Main() because mono already uses different glib functions internally and it
+must be called before the first glib function.
+See http://bugzilla.gnome.org/show_bug.cgi?id=331853 for more informations.
+With glib 2.13 almost every bigger mono application prints this warning on
+GSlice: g_thread_init() must be called before all other GLib functions;
+memory corruption due to late invocation of g_thread_init() has been
+detected; this program is likely to crash, leak or unexpectedly abort soon...

More information about the mono-bugs mailing list