Bug 13788 - Task.Delay does not return after first call
Summary: Task.Delay does not return after first call
Status: RESOLVED DUPLICATE of bug 13318
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 4.8.x
Hardware: PC Mac OS
: --- normal
Target Milestone: ---
Assignee: Marek Safar
Depends on:
Reported: 2013-08-06 16:06 UTC by Bryan Moulton
Modified: 2013-08-16 11:31 UTC (History)
2 users (show)

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

Scroll Sample (17.84 KB, application/zip)
2013-08-06 16:06 UTC, Bryan Moulton

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 Developer Community or GitHub 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 Bryan Moulton 2013-08-06 16:06:27 UTC
Created attachment 4557 [details]
Scroll Sample

In reference to case #43245

Refer to the test project included. DemoAdapter.LoadData is called when the user scrolls to the bottom of the list. When this is called a second time, Task.Delay never returns which causes the execution of EndlessAdapter.ExecuteItemLoadAsync to halt indefinitely.
Comment 1 Jonathan Pryor 2013-08-15 17:29:17 UTC
Marek: Any thoughts on what I should investigate here? I have no idea why the 2nd Task.Delay() would never return... :-(
Comment 2 Marek Safar 2013-08-16 11:31:45 UTC
Should be already fixed in newer alphas

*** This bug has been marked as a duplicate of bug 13318 ***