System.Net.Sockets.SocketException Crash On net6.0 #57498
Unanswered
drearyrainDeng
asked this question in
General
Replies: 1 comment 3 replies
-
This is unlikely to be backported to .NET 6 at this stage given that it goes out of support in November. |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I facing some crash due to System.Net.Sockets.SocketException on some custom pc(win7sp1). And i opened a issue #56839 before. look at the source code ,It is changed since to net7.0. is it possible backport #38094 to net6.0 ? It should be able to avoid crashes even if it reports errors。Thank you for any help!
some dump trace as below:
[0x0] KERNELBASE!RaiseException+0x58 0x7031f364 0x2d93bac
[0x1] coreclr!RaiseTheExceptionInternalOnly+0x146 0x7031f3bc 0x2d93556
[0x2] coreclr!IL_Throw+0x86 0x7031f468 0x24d1d16
[0x3] Microsoft_AspNetCore_Server_Kestrel_Transport_Sockets!Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.Internal.SocketAwaitableEventArgs.g__ThrowSocketException|5_0+0x16 0x7031f500 0x6f801ca
[0x4] Microsoft_AspNetCore_Server_Kestrel_Transport_Sockets!Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.Internal.SocketAwaitableEventArgs.GetResult+0x1a 0x7031f50c 0x6f6da35
[0x5] Microsoft_AspNetCore_Server_Kestrel_Transport_Sockets!Microsoft.AspNetCore.Server.Kestrel.Transport.Sockets.Internal.SocketConnection.d__28.MoveNext+0x175 0x7031f510 0x6f8019a
[0x6] System_Private_CoreLib!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<System.Threading.Tasks.VoidTaskResult>.AsyncStateMachineBox<d__28>.ExecutionContextCallback+0xa 0x7031f5c0 0x3e99149a
[0x7] System_Private_CoreLib!System.Threading.ExecutionContext.RunInternal+0x5a 0x7031f5c4 0x6f800bc
[0x8] System_Private_CoreLib!System.Runtime.CompilerServices.AsyncTaskMethodBuilder<System.Threading.Tasks.VoidTaskResult>.AsyncStateMachineBox<d__28>.MoveNext+0xac 0x7031f5fc 0xcbfffc7
Beta Was this translation helpful? Give feedback.
All reactions