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=77847 --- shadow/77847 2006-12-17 02:14:45.000000000 -0500 +++ shadow/77847.tmp.7317 2006-12-17 09:09:35.000000000 -0500 @@ -1,13 +1,13 @@ Bug#: 77847 Product: Mono: Class Libraries Version: 1.1 OS: unknown OS Details: -Status: NEW -Resolution: +Status: RESOLVED +Resolution: FIXED Severity: Unknown Priority: Minor Component: System AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] QAContact: [EMAIL PROTECTED] @@ -187,6 +187,21 @@ Is there some way I can modify the timer class to trap the offending thread to see what the timing is that causes the issue? Could there still be a race in the timer? Chris + +------- Additional Comments From [EMAIL PROTECTED] 2006-12-17 09:09 ------- +I ran some test on the MS.NET runtime. It's definitely not +thread safe. I was able to reproduce the same races like +in Mono. + +Maybe you're locking on the wrong object, or not locking +at all at some places. + +Note that inserting a null check at line 192 of Timers.cs +won't fix anything. It would hide (not cure) a race generated by +the Timer's consumer. + +Chris, feel free to reopen the bug, if you have a test case. + _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
