[Mono-bugs] [Bug 77847][Min] Changed - [PATCH] "Too many threads" error when starting and stopping a timer repeatedly

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Sun Dec 17 09:09:36 EST 2006

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.


--- shadow/77847	2006-12-17 02:14:45.000000000 -0500
+++ shadow/77847.tmp.7317	2006-12-17 09:09:35.000000000 -0500
@@ -1,13 +1,13 @@
 Bug#: 77847
 Product: Mono: Class Libraries
 Version: 1.1
 OS: unknown
 OS Details: 
-Status: NEW   
+Status: RESOLVED   
+Resolution: FIXED
 Severity: Unknown
 Priority: Minor
 Component: System
 AssignedTo: robertj at gmx.net                            
 ReportedBy: paul.hudson at gmail.com               
 QAContact: mono-bugs at ximian.com
@@ -187,6 +187,21 @@
 Is there some way I can modify the timer class to trap the offending
 thread to see what the timing is that causes the issue? Could there
 still be a race in the timer?
+------- Additional Comments From robertj at gmx.net  2006-12-17 09:09 -------
+I ran some test on the MS.NET runtime. It's definitely not
+thread safe. I was able to reproduce the same races like
+in Mono.
+Maybe you're locking on the wrong object, or not locking
+at all at some places.
+Note that inserting a null check at line 192 of Timers.cs
+won't fix anything. It would hide (not cure) a race generated by
+the Timer's consumer.
+Chris, feel free to reopen the bug, if you have a test case.

More information about the mono-bugs mailing list