System.Net.Sockets.SocketException (10014): The system detected an invalid pointer address in attempting to use a pointer argument in a call #92464
Comments
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsDescriptionI've created an IoTEdge module, which is an application containerized using Docker, and initially, it was built with dotnet core version 3.1. We've been using this module for a considerable amount of time. However, as part of our security team's recommendations, we decided to migrate it to dotnet core version 7.0. After making this migration, we encountered a System.Net.Socket.SocketException when running the modules. We attempted to test it with dotnet core 6.0 as well, but unfortunately, we faced the same issue. Consequently, we reverted the Docker base image back to version 3.1, and the module started functioning correctly. I'm sharing the exception details for additional information. Reproduction StepsWe are not able to upgrade the application to latest dotnet core version although it works fine with dotnet core 3.1, No specific steps for reproduction Expected behaviorApplication should work as is as they works in dotnet core 3.1 Actual behaviorIt gives an exceptions Regression?No response Known WorkaroundsNo workarounds with dotnet core 7.0 ConfigurationDotnet Core 7.0 Other informationWe are using iotedge device sdk to initialize the modules. While initializing the modules we are getting this exception.
|
|
Be aware that .NET Core 3.1 is out of support for almost a year now: https://github.com/dotnet/core/blob/main/releases.md#end-of-life-net-versions Can you confirm that it reproduces always? Source code reference: Microsoft.Azure.Devices.Client.HsmAuthentication.Transport.HttpUdsMessageHandler.GetConnectedSocketAsync Are you using latest version of azure-iot-sdk? (whichever the version is) Are you able to create minimal repro? (i.e. remove as much code as you can to keep it still failing) |
|
Tagging subscribers to this area: @dotnet/ncl Issue DetailsDescriptionI've created an IoTEdge module, which is an application containerized using Docker, and initially, it was built with dotnet core version 3.1. We've been using this module for a considerable amount of time. However, as part of our security team's recommendations, we decided to migrate it to dotnet core version 7.0. After making this migration, we encountered a System.Net.Socket.SocketException when running the modules. We attempted to test it with dotnet core 6.0 as well, but unfortunately, we faced the same issue. Consequently, we reverted the Docker base image back to version 3.1, and the module started functioning correctly. We uses following docker image for our application I'm sharing the exception details for additional information. Reproduction StepsWe are not able to upgrade the application to latest dotnet core version although it works fine with dotnet core 3.1, No specific steps for reproduction Expected behaviorApplication should work as is as they works in dotnet core 3.1 Actual behaviorIt gives an exceptions Regression?No response Known WorkaroundsNo workarounds with dotnet core 7.0 ConfigurationDotnet Core 7.0 Other informationWe are using iotedge device sdk to initialize the modules. While initializing the modules we are getting this exception.
|
|
I would suspect that WSAEFAULT is happening because @niravjprabtani do you know if this is running against the NETSTANDARD2_0 build of the Azure SDK? Their built in It should be 110: @wfurt any thoughts? |
antonfirsov
removed
the
untriaged
|
@niravjprabtani what hardware/architecture is this running on? What is the exact OS version? As stated in #92464 (comment), a repro would really help a lot. Also: did you update the IoT SDK together with the 3.1->6.0 update? We would need to know the SDK versions before/after. ( |
|
I think the UDS size would matter only if we are reaching the file length limits. If this is reproducible, it may worth of trying to get coredump And use runtime's build-in type. Even there, there were some more fixes in 8.0 and it may be worth of shoot. |
antonfirsov
added
the
needs-author-action
|
This issue has been marked |
|
This issue has been automatically marked |
|
This issue will now be closed since it had been marked |
ghost
locked as resolved and limited conversation to collaborators
Description
I've created an IoTEdge module, which is an application containerized using Docker, and initially, it was built with dotnet core version 3.1. We've been using this module for a considerable amount of time. However, as part of our security team's recommendations, we decided to migrate it to dotnet core version 7.0. After making this migration, we encountered a System.Net.Socket.SocketException when running the modules. We attempted to test it with dotnet core 6.0 as well, but unfortunately, we faced the same issue. Consequently, we reverted the Docker base image back to version 3.1, and the module started functioning correctly.
We uses following docker image for our application
FROM mcr.microsoft.com/dotnet/sdk:7.0
I'm sharing the exception details for additional information.
Reproduction Steps
We are not able to upgrade the application to latest dotnet core version although it works fine with dotnet core 3.1, No specific steps for reproduction
Expected behavior
Application should work as is as they works in dotnet core 3.1
Actual behavior
It gives an exceptions
Regression?
No response
Known Workarounds
No workarounds with dotnet core 7.0
Configuration
Dotnet Core 7.0
Docker Windows X64
Other information
We are using iotedge device sdk to initialize the modules. While initializing the modules we are getting this exception.
The text was updated successfully, but these errors were encountered: