[Mono-bugs] [Bug 81982][Nor] New - Failing to call EndInvoke on a delegate causes apps to hang on exit

[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 dave at fallingcanbedeadly.com.

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

--- shadow/81982	2007-06-30 18:12:43.000000000 -0400
+++ shadow/81982.tmp.9177	2007-06-30 18:12:43.000000000 -0400
@@ -0,0 +1,41 @@
+Bug#: 81982
+Product: Mono: Class Libraries
+Version: 1.2
+OS: Mac OS X 10.3
+OS Details: Actually running 10.4, but there's no option for that
+Status: NEW   
+Resolution: 
+Severity: 
+Priority: Normal
+Component: CORLIB
+AssignedTo: mono-bugs at ximian.com                            
+ReportedBy: dave at fallingcanbedeadly.com               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+URL: 
+Cc: 
+Summary: Failing to call EndInvoke on a delegate causes apps to hang on exit
+
+Please fill in this template when reporting a bug, unless you know what you are doing.
+Description of Problem:
+I haven't verified this on any other platform, but on the Macintosh, Failing to call EndInvoke on a 
+delegate after calling BeginInvoke will cause the app to hang when it tries to return.
+
+Steps to reproduce the problem:
+1. Run the test delegate1.exe on the Mac
+2. Watch it hang because it doesn't call EndInvoke (inserting proper calls to EndInvoke before 
+returning will fix this issue)
+3. 
+
+Actual Results:
+The app hangs
+
+Expected Results:
+MSDN documentation states that you should *always* call EndInvoke after calling BeginInvoke, so 
+delegate1.cs should probably be updated to reflect best practices. On the other hand, mono 
+probably shouldn't hang if this doesn't happen.
+
+How often does this happen? 
+Always
+
+Additional Information: