[Mono-bugs] [Bug 78139][Nor] Changed - Bad implementation of SynchronizationContext.Post()

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Wed Apr 19 04:52:02 EDT 2006

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


--- shadow/78139	2006-04-19 04:08:26.000000000 -0400
+++ shadow/78139.tmp.25155	2006-04-19 04:52:02.000000000 -0400
@@ -1,14 +1,14 @@
 Bug#: 78139
 Product: Mono: Class Libraries
 Version: unspecified
+OS: unknown
 OS Details: 
 Status: NEW   
+Severity: Unknown
 Priority: Normal
 Component: CORLIB
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: flipper98 at gmx.net               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -31,6 +31,14 @@
 A proper implemetation would call:
 ThreadPool.QueueUserWorkItem(new WaitCallback(d), state);
 The difference being that ThreadPool.QueueUserWorkItem() will not suppress
 exceptions thrown by the WaitCallback delegate (assumed mono implements
 ThreadPool.QueueUserWorkItem correctly(?)).
+------- Additional Comments From atsushi at ximian.com  2006-04-19 04:52 -------
+What is similarly important is that SynchronizationContext.Post() does
+not seem to run the callback synchronously (Post() itself should
+return asynchronously but the callback execution should be synchronous).
+It affects on System.ComponentModel.BackgroundWorker behavior. (I also
+doubt this problem goes away by using ThreadPool.QueueUserWorkItem()).

More information about the mono-bugs mailing list