Bug 47433 - HTTP remoting tests fail with "Cannot access a disposed object"
Summary: HTTP remoting tests fail with "Cannot access a disposed object"
Status: RESOLVED FIXED
Alias: None
Product: Class Libraries
Classification: Mono
Component: System ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: Untriaged
Assignee: Marek Safar
URL:
Depends on:
Blocks:
 
Reported: 2016-11-18 22:09 UTC by Andi McClure
Modified: 2016-11-22 17:17 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 Andi McClure 2016-11-18 22:09:27 UTC
A variety of tests related to HTTP and remoting are failing with this managed exception

                                                MESSAGE:
                                                System.Net.WebException : Cannot access a disposed object.
Object name: 'System.Net.Sockets.NetworkStream'.
  ----> System.ObjectDisposedException : Cannot access a disposed object.
Object name: 'System.Net.Sockets.NetworkStream'.

Examples:

HttpDelegateCallTest.BaseCallTest.TestInstanceProcessContextData

https://jenkins.mono-project.com/job/test-mono-mainline-linux/label=ubuntu-1404-amd64/1214/testReport/(root)/HttpDelegateCallTest/BaseCallTest_TestInstanceProcessContextData/
https://jenkins.mono-project.com/job/test-mono-mainline-linux/label=ubuntu-1404-amd64/1214/testReport/(root)/HttpDelegateCallTest/BaseCallTest_TestInstanceProcessContextData/

HttpBinarySyncCallTest.BaseCallTest.TestAbstractProcessContextData

https://jenkins.mono-project.com/job/test-mono-mainline-linux/label=ubuntu-1404-i386/1216/testReport/(root)/HttpBinarySyncCallTest/BaseCallTest_TestAbstractProcessContextData/

HttpSyncCallTest.BaseCallTest.TestInterfaceProcessContextData

https://jenkins.mono-project.com/job/test-mono-mainline-linux/label=ubuntu-1404-amd64/1191/testReport/(root)/HttpSyncCallTest/BaseCallTest_TestInterfaceProcessContextData/
Comment 1 Andi McClure 2016-11-18 22:10:26 UTC
Note, three out of four of these occurred on ARM64. One was on Intel32. There are other related tests failing, these are just the four I scrounged.

Also note this may be related to bug #47424 which also concerns socket disposal issues in remoting and which seems to have appeared at roughly the same time. That one was seen on ARM64 only.
Comment 2 Marek Safar 2016-11-22 17:17:10 UTC
Should be fixed