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 [EMAIL PROTECTED] http://bugzilla.ximian.com/show_bug.cgi?id=79484 --- 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 +Resolution: +Severity: +Priority: Wishlist +Component: System +AssignedTo: [EMAIL PROTECTED] +ReportedBy: [EMAIL PROTECTED] +QAContact: [EMAIL PROTECTED] +TargetMilestone: --- +URL: +Cc: +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 1.1.13.8. + +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" +code. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
