[Mono-bugs] [Bug 81974][Nor] Changed - GC crashes if there are more than about 160 threads.
bugzilla-daemon at bugzilla.ximian.com
bugzilla-daemon at bugzilla.ximian.com
Fri Jun 29 20:01:27 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 robertj at gmx.net.
http://bugzilla.ximian.com/show_bug.cgi?id=81974
--- shadow/81974 2007-06-28 21:28:38.000000000 -0400
+++ shadow/81974.tmp.21064 2007-06-29 20:01:27.000000000 -0400
@@ -3,13 +3,13 @@
Version: 1.2
OS: All
OS Details:
Status: NEW
Resolution:
Severity: Unknown
-Priority: Critical
+Priority: Normal
Component: GC
AssignedTo: lupus at ximian.com
ReportedBy: patperry at stanford.edu
QAContact: mono-bugs at ximian.com
TargetMilestone: ---
URL:
@@ -101,6 +101,14 @@
** (ThreadBug.exe:23353): WARNING **: _wapi_thread_abandon_mutexes:
error looking up thread handle 0x998
** (ThreadBug.exe:23353): WARNING **:
_wapi_thread_set_termination_details: error looking up thread handle 0x998
+
+------- Additional Comments From robertj at gmx.net 2007-06-29 20:01 -------
+The second issue might be io-layer related: if the GC doesn't collect
+the thread objects fast enough, the io-layer is running out
+of handles, since their max count is static (4K)).
+
+Changed prio (see http://bugzilla.ximian.com/bug_status.html#priority)
+
More information about the mono-bugs
mailing list