[Mono-bugs] [Bug 60576][Maj] Changed - Bad interaction - Mono, Gentoo (nptl) & Muine

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Fri, 10 Sep 2004 01:07:55 -0400 (EDT)


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 scott.mohekey@telogis.com.

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

--- shadow/60576	2004-09-08 14:39:10.000000000 -0400
+++ shadow/60576.tmp.2673	2004-09-10 01:07:55.000000000 -0400
@@ -496,6 +496,23 @@
         NPTL 0.61 by Ulrich Drepper
         BIND-8.2.3-T5B
         NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
 Thread-local storage support included.
 Report bugs using the `glibcbug' script to <bugs@gnu.org>.
 
+
+------- Additional Comments From scott.mohekey@telogis.com  2004-09-10 01:07 -------
+In my research into this bug, I've managed to find that the freeze
+occurs when libgc is performing a garbage collection. If you run the
+test class listed above with the environment variable GC_PRINT_STATS
+set, you will see that the very last output to the console is
+"Initiating full world-stop collection <x> after <y> allocd bytes"
+
+I've also verified that the issue with xsp freezing is related, the
+same message is printed when it freezes on an nptl enabled glibc.
+
+At this point in time, all threads are in a wait state.
+
+An interesting thing I found out is that if you set a breakpoint in
+the libgc code that prints the message, it will be continuously hit
+once the app has frozen. And in some cases I even saw the garbage
+collector repeatedly trying to collect the same identical heap.