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

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Sun Sep 24 15:35:36 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-24 15:35:36.000000000 -0400
+++ shadow/79484.tmp.16567	2006-09-24 15:35:36.000000000 -0400
@@ -0,0 +1,35 @@
+Bug#: 79484
+Product: Mono: Class Libraries
+Version: 1.1
+OS: Red Hat 9.0
+OS Details: RHEL 4
+Status: NEW   
+Priority: Wishlist
+Component: System
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: psingh at fnfr.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: null reference exception in System.Timers.StartTimer()
+We are intermittently getting null reference exception message:
+System.NullReferenceException: Object reference not set to an instance of
+an object
+in <0x000e0> System.Timers.Timer:StartTimer ()
+in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void ()
+Machine is Red Hat Enterprise Linux 4. Mono is
+Since the exception is not in our code but inside the class library, we
+need desperately a work around or a fix for it.
+How often does this happen? 
+Very often - on one machine it happens 99% of the time, on another it
+happens 50% of the time. I tried running our app with mono -v option to get
+more information, but it prints mostly useless information about "emitting"

More information about the mono-bugs mailing list