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

[bugzilla-daemon at bugzilla.ximian.com]

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.

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

--- shadow/77847	2006-12-11 16:42:59.000000000 -0500
+++ shadow/77847.tmp.9486	2006-12-14 23:47:59.000000000 -0500
@@ -116,6 +116,20 @@
 ------- Additional Comments From robertj at gmx.net  2006-12-11 16:30 -------
 Fixed in SVN 69357.
 
 
 ------- Additional Comments From robertj at gmx.net  2006-12-11 16:42 -------
 *** Bug 79484 has been marked as a duplicate of this bug. ***
+
+------- Additional Comments From cmorgan at alum.wpi.edu  2006-12-14 23:47 -------
+Robert, is there still a race condition in System.Timers.Timer?
+
+Unhandled Exception: System.NullReferenceException: Object reference
+not set to an instance of an object
+  at System.Timers.Timer.StartTimer () [0x0005e] in
+/home/cmorgan/mono/mcs/class/System/System.Timers/Timer.cs:192
+  at (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()
+
+I get this when running with an application that uses a lot of timers
+with svn head from tonight, 20061214 (r69515)
+
+Chris