[Mono-bugs] [Bug 78652][Nor] Changed - [2.0] Control.BeginInvoke crashes if security not enabled.

[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 sebastien at ximian.com.

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

--- shadow/78652	2006-06-15 07:21:08.000000000 -0400
+++ shadow/78652.tmp.3742	2006-06-15 10:00:15.000000000 -0400
@@ -2,22 +2,22 @@
 Product: Mono: Class Libraries
 Version: 1.1
 OS: Debian Woody
 OS Details: Debian Sid
 Status: NEW   
 Resolution: 
-Severity: 
-Priority: Major
+Severity: Unknown
+Priority: Normal
 Component: Windows.Forms
-AssignedTo: peter at novonyx.com                            
+AssignedTo: sebastien at ximian.com                            
 ReportedBy: tilps.kilm at gmail.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
 URL: 
 Cc: 
-Summary: Control.BeginInvoke crashes in .net 2.0 profile if security not enabled.
+Summary: [2.0] Control.BeginInvoke crashes if security not enabled.
 
 Description of Problem:
 Control.BeginInvokeInternal sets the asyncMethodData.context regardless of
 whether security is enabled.  But if security is not enabled, the security
 context within the execution context does not have its CompressedStack
 setup, therefore using the ExecutionContext.Run method results in a null
@@ -31,6 +31,11 @@
 set. (Patch attached...)
 
 ------- Additional Comments From tilps.kilm at gmail.com  2006-06-15 07:21 -------
 Created an attachment (id=17191)
 Patch to fix this issue.
 
+
+------- Additional Comments From sebastien at ximian.com  2006-06-15 10:00 -------
+The CompressedStack change (return empty) is a recent fix for bug
+#78306. I think the fix should be done in ExecutionContext (and will
+look at that) as, in a perfect world, MWF shouldn't have to consider this.