[Mono-bugs] [Bug 77847][Min] Changed - "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 robertj at gmx.net.

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

--- shadow/77847	2006-03-18 19:58:33.000000000 -0500
+++ shadow/77847.tmp.5802	2006-03-18 21:12:49.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 77847
 Product: Mono: Runtime
 Version: 1.1
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Minor
 Component: GC
 AssignedTo: lupus at ximian.com                            
 ReportedBy: paul.hudson at gmail.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -45,6 +45,23 @@
 across the problem.
 
 ------- Additional Comments From paul.hudson at gmail.com  2006-03-18 19:58 -------
 Created an attachment (id=16642)
 Simplified test case using one timer
 
+
+------- Additional Comments From robertj at gmx.net  2006-03-18 21:12 -------
+There are some race conditions in System.Timers.Timer:
+
+1. The wait handle used by StopTimer is sometimes null,
+   because the new thread didn't make so far to create
+   the handle while you app already called Stop().
+
+2. Even when the wait handle isn't null, since there
+   is no Join call on the thread, the wait handle can
+   be overriden be the next starting thread.
+
+The problems occur on Windows due to the different
+threading implementions.
+
+I'll provide a patch.
+