Bug 18121 - LocalCallContext is not captured by ThreadPool and new Thread()
Summary: LocalCallContext is not captured by ThreadPool and new Thread()
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: 3.2.x
Hardware: PC Windows
: --- normal
Target Milestone: Untriaged
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2014-03-03 07:23 UTC by Alexey Yakovlev
Modified: 2014-03-06 13:54 UTC (History)
3 users (show)

Tags:
Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and 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 Links.

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.

Related Links:
Status:
RESOLVED FIXED

Description Alexey Yakovlev 2014-03-03 07:23:33 UTC
Logical call context should be transferred (as a part of execution context)
when a new thread is created. Here is a quote from MSDN:

http://msdn.microsoft.com/en-us/library/system.threading.executioncontext(v=vs.110).aspx

>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:

https://gist.github.com/yallie/9323777
Comment 1 Alexander Köplinger 2014-03-05 14:16:45 UTC
There's currently a pull request pending that might fix this: https://github.com/mono/mono/pull/864
Comment 2 Marek Safar 2014-03-06 13:54:11 UTC
Fixed in master