Bug 42181 - SocketTest.SendAsyncFile failure (ObjectDisposedException) on Android
Summary: SocketTest.SendAsyncFile failure (ObjectDisposedException) on Android
Status: VERIFIED FIXED
Alias: None
Product: Runtime
Classification: Mono
Component: io-layer ()
Version: 4.6.0 (C8)
Hardware: Other Other
: Normal major
Target Milestone: 4.6.0 (C8)
Assignee: marcos.henrich
URL:
Depends on:
Blocks:
 
Reported: 2016-06-27 08:24 UTC by Alex Rønne Petersen
Modified: 2016-08-29 12:40 UTC (History)
4 users (show)

Tags:
Is this bug a regression?: Yes
Last known good build: f4a3cbdaed28348cdc7c79ee7091ccca012e4fe5

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:
VERIFIED FIXED

Description Alex Rønne Petersen 2016-06-27 08:24:11 UTC
As of the bump from mono-4.5.1-branch commit f4a3cbdaed28348cdc7c79ee7091ccca012e4fe5 to dd63bc4cdaf6ca374619a1ef04e18f4453a29f5b, we're seeing the following failure consistently on Android:

> E/mono    ( 2201): Unhandled Exception:
> E/mono    ( 2201): System.ObjectDisposedException: Cannot access a disposed object.
> E/mono    ( 2201): Object name: 'System.Net.Sockets.Socket'.
> E/mono    ( 2201):   at System.Net.Sockets.Socket.ThrowIfDisposedAndClosed () [0x00016] in /Users/builder/data/lanes/1196/5a5543c3/source/mono/mcs/class/System/System.Net.Sockets/Socket.cs:3373 
> E/mono    ( 2201):   at System.Net.Sockets.Socket.EndSendFile (System.IAsyncResult asyncResult) [0x00000] in /Users/builder/data/lanes/1196/5a5543c3/source/mono/mcs/class/System/System.Net.Sockets/Socket.cs:2929 
> E/mono    ( 2201):   at MonoTests.System.Net.Sockets.SocketTest+<SendAsyncFile>c__AnonStorey2.<>m__0 (System.IAsyncResult ar) [0x0000f] in /Users/builder/data/lanes/1196/5a5543c3/source/monodroid/tests/bcl-test/src/System/Test/System.Net.Sockets/SocketTest.cs:4269 
> E/mono    ( 2201):   at System.Net.Sockets.Socket+<BeginSendFile>c__AnonStorey3.<>m__0 (System.IAsyncResult ar) [0x00000] in /Users/builder/data/lanes/1196/5a5543c3/source/mono/mcs/class/System/System.Net.Sockets/Socket.cs:2924 
> E/mono    ( 2201):   at (wrapper managed-to-native) System.Runtime.Remoting.Messaging.AsyncResult:Invoke (System.Runtime.Remoting.Messaging.AsyncResult)
> E/mono    ( 2201):   at System.Runtime.Remoting.Messaging.AsyncResult.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00000] in /Users/builder/data/lanes/1196/5a5543c3/source/mono/mcs/class/corlib/System.Runtime.Remoting.Messaging/AsyncResult.cs:213 
> E/mono    ( 2201):   at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00096] in /Users/builder/data/lanes/1196/5a5543c3/source/mono/mcs/class/referencesource/mscorlib/system/threading/threadpool.cs:855 
> E/mono    ( 2201):   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in /Users/builder/data/lanes/1196/5a5543c3/source/mono/mcs/class/referencesource/mscorlib/system/threading/threadpool.cs:1210
Comment 1 Alex Rønne Petersen 2016-08-29 08:47:20 UTC
This failure doesn't seem to occur anymore.
Comment 2 Mohit Kheterpal 2016-08-29 12:40:27 UTC
As per comment 1, this issue seems to be fixed for Alex Rønne Petersen.

Hence closing this issue by marking it as Verified.

thanks