Bug 2569 - Repetitively sending and receiving data over TCP causes eventual device hangs
Summary: Repetitively sending and receiving data over TCP causes eventual device hangs
Alias: None
Product: Android
Classification: Xamarin
Component: Mono runtime / AOT Compiler ()
Version: 4.0
Hardware: All All
: Normal normal
Target Milestone: ---
Assignee: Marek Habersack
Depends on:
Reported: 2011-12-19 12:29 UTC by James Clayton
Modified: 2016-09-01 19:10 UTC (History)
4 users (show)

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

samle reproduction of the bug (353.05 KB, application/octet-stream)
2011-12-19 12:29 UTC, James Clayton

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 James Clayton 2011-12-19 12:29:24 UTC
Created attachment 1069 [details]
samle reproduction of the bug

Repeated calls to send and receive data over TCP causes applications to eventually freeze with a "Wait / Force Close" dialog. No exception is thrown. When running in debug mode, the debugger disconnects and there is nothing apparently related showing in the device log.

The period between the app starting and the app freezing varies though the average appears to be related to the interval at which data is sent.

With data being sent every 5 seconds, the crash appears to occur at any point between 2 minutes and 6 hours.

With data being sent every 10 seconds, the crash may not occur for 12 or more hours.

I have attached a sample project which replicates the problem.

The app has been tested and the issue confirmed to occur both on a Samsung Galaxy S with the 2.3 kernel update, and a generic Chinese phone running on Android 2.2
Comment 1 Marek Habersack 2016-09-01 19:10:34 UTC
Tested with the current monodroid/master (70dc4f2a9852c8a72e88c51f8e4e48d396f28e7d) and the issue was not reproducible. The sample did eventually crash but with a NullReferenceException in the sample code - unrelated to the OP's report.