-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reusing SocketAsyncEventArgs
for multiple calls to the static Socket.Connect()
#8871
Labels
Comments
You may have to run this on a Mac where |
There's another problem when using
|
Added some more tests to web-tests/Xamarin.WebTests.SocketTests. |
Unfortunately, that doesn't fix the problem. |
baulig
pushed a commit
to baulig/mono
that referenced
this issue
May 29, 2018
baulig
pushed a commit
to baulig/mono
that referenced
this issue
May 29, 2018
akoeplinger
pushed a commit
that referenced
this issue
Jun 13, 2018
monojenkins
pushed a commit
to monojenkins/mono
that referenced
this issue
Jun 13, 2018
monojenkins
pushed a commit
to monojenkins/mono
that referenced
this issue
Jun 13, 2018
akoeplinger
pushed a commit
that referenced
this issue
Jun 18, 2018
UnityAlex
pushed a commit
to Unity-Technologies/mono
that referenced
this issue
Sep 3, 2019
UnityAlex
pushed a commit
to Unity-Technologies/mono
that referenced
this issue
Sep 6, 2019
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using the static
Socket.Connect()
multiple times with the sameSocketAsyncEventArgs
throwsSimple example:
This works fine on .NET.
Full test case:
A.cs
This is a problem because the new
System.Net.Http
code from CoreFX is reusingSocketAsyncEventArgs
instances.The text was updated successfully, but these errors were encountered: