Bug 26772 - TaskScheduler.Current resets to default after await
Summary: TaskScheduler.Current resets to default after await
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: 3.12.0
Hardware: PC All
: --- normal
Target Milestone: Untriaged
Assignee: Marek Safar
Depends on:
Reported: 2015-02-05 09:22 UTC by Rohan Singh
Modified: 2015-02-06 08:39 UTC (History)
2 users (show)

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

test project (8.60 KB, application/x-zip-compressed)
2015-02-05 09:22 UTC, Rohan Singh

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:

Description Rohan Singh 2015-02-05 09:22:56 UTC
Created attachment 9660 [details]
test project

When using a custom TaskScheduler, TaskScheduler.Current value will sometimes reset to its default value after an await.

The issue can be seen here: http://ideone.com/pWX2jN

The output at the bottom shows TaskScheduler.Current changes after an await. This does not happen when running on .NET.
Comment 1 Marek Safar 2015-02-06 08:39:45 UTC
Already fixed in master