Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
GitHub or Developer Community with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Logical call context should be transferred (as a part of execution context)
when a new thread is created. Here is a quote from MSDN:
>Within an application domain, the entire execution context must be transferred
>whenever a thread is transferred. This situation occurs during transfers made by
>the Thread.Start method, most thread pool operations, and Windows Forms thread
>marshaling through the Windows message pump.
>Internally, the ExecutionContext stores all data that is associated with the LogicalCallContext.
>This allows the LogicalCallContext data to be propagated when the ExecutionContext is copied and transferred.
The following code works on Microsoft.NET but doesn't work on Mono 3.2.x:
There's currently a pull request pending that might fix this: https://github.com/mono/mono/pull/864
Fixed in master