[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
Sat Nov 25 19:49:33 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 cmorgan at alum.wpi.edu.


--- shadow/77847	2006-10-09 10:03:49.000000000 -0400
+++ shadow/77847.tmp.26065	2006-11-25 19:49:33.000000000 -0500
@@ -84,6 +84,21 @@
 ------- Additional Comments From psingh at fnfr.com  2006-09-26 19:17 -------
 I see that this bug is still open. I got latest trunk code and this
 bug has not been fixed. Why will Mono guys not take this bug fix?
 ------- Additional Comments From dick at ximian.com  2006-10-09 10:03 -------
 Because other work has taken priority
+------- Additional Comments From cmorgan at alum.wpi.edu  2006-11-25 19:49 -------
+This patch fixes a problem I was seeing with lots of timers on mono
+svn head(r68140):
+Unhandled Exception: System.NullReferenceException: Object reference
+not set to an instance of an object
+  at System.Timers.Timer.StartTimer () [0x0005d] in
+  at (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()
+Timers appear to work as well as they did with and without this patch
+but I haven't run any of the test suite after applying it.

More information about the mono-bugs mailing list