Bug 11908 - Task.Yield() not continuing on context
Summary: Task.Yield() not continuing on context
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: mscorlib ()
Version: unspecified
Hardware: Macintosh Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2013-04-23 12:09 UTC by Lance Bullock
Modified: 2013-04-24 04:33 UTC (History)
2 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 Lance Bullock 2013-04-23 12:09:23 UTC
This is on the Beta 4.0.4 running on iOS.

When I await Task.Yield() my understanding is that the continuation code after the await should resume on the captured context (in this case the UI thread). It does not appear this is happening, can be reproduced simply by dumping the NSThread current thread description, awaiting Task.Yield() and then dumping the NSThread currentThread description again - you will see they are different thread objects. More obviously, and UI code in the continuation will throw a UIKit exception that the UI is not being accessed from the UI thread.
Comment 1 Marek Safar 2013-04-24 04:33:01 UTC
Fixed in master (next beta should include the fix)