Bug 38634 - CancellationToken timeout not being applied when in background.
Summary: CancellationToken timeout not being applied when in background.
Status: RESOLVED ANSWERED
Alias: None
Product: Android
Classification: Xamarin
Component: General ()
Version: 5.1
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Marek Habersack
URL:
Depends on:
Blocks:
 
Reported: 2016-02-10 15:17 UTC by stewart_short
Modified: 2016-08-31 21:52 UTC (History)
1 user (show)

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


Attachments
More detailed explanation and partial traces (135.50 KB, application/msword)
2016-02-10 15:17 UTC, stewart_short
Details


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:
Status:
RESOLVED ANSWERED

Description stewart_short 2016-02-10 15:17:27 UTC
Created attachment 14984 [details]
More detailed explanation and partial traces

When using a CancellationToken to set the timeout on an FtpWebRequest, the TaskCanceledException is successfully raised after the defined timeout when in the foreground (5 minutes in this case), but when the application is in the background the TaskcanceledException is being raised only after 90 minutes plus.
Comment 1 stewart_short 2016-02-11 18:11:27 UTC
After more investigation I believe it is when the phone Samsung Note 4 goes into Lock/Sleep Mode, rather than just the app being backgrounded.
Comment 2 Marek Habersack 2016-08-31 21:51:51 UTC
I don't believe we can call this issue a bug. This is due to the fact that Android doesn't give any guarantees that a background process (defined as one without a foreground activity - that is all activities of the application/process had their OnStop handler called) will ever remain alive (please see this article https://developer.android.com/guide/components/processes-and-threads.html). In such instance Mono, the Xamarin.Android runtime, cannot deliver the promise of cancelling of an operation within the indicated frame of time.
To make your scenario work you should consider creating a *service process* (also described in the above article) which *should not* be killed by the system unless an out-of-memory situation arises.