[Mono-bugs] [Bug 79484][Nor] Changed - null reference exception in System.Timers.StartTimer()

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Sep 27 02:11:38 EDT 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 psingh at fnfr.com.


--- shadow/79484	2006-09-26 19:19:05.000000000 -0400
+++ shadow/79484.tmp.10737	2006-09-27 02:11:38.000000000 -0400
@@ -68,6 +68,24 @@
 ------- Additional Comments From psingh at fnfr.com  2006-09-26 19:19 -------
 The patch in 77847 was submitted 6 months ago. I did a get latest
 today (09/26/2006) and it has not made it in there. Why are Mono guys
 not taking the patch? This seems to be a big problem with Timers code.
+------- Additional Comments From psingh at fnfr.com  2006-09-27 02:11 -------
+Actually the problem is more insidious than that. The Crash is on the
+following line in method StartTimer():
+==>((IDisposable) wait).Dispose ();
+I traced it down into the mono library call - in WaitHandle.cs:Dispose()
+NativeEventCalls.CloseEvent_internal (os_handle);
+Somehow, the underlying mono platform code on RHEL 4.0 has problems
+when  the app creates tonnes of threads, events, timers.
+Is anyone going to look into it? We can reproduce it at will right now
+ and it will be great if a Mono developer can "breeze" into our
+computers and take a look.

More information about the mono-bugs mailing list