tony

This does appear to only be an issue with the Windows native DNS resolver when using short name (localnames) and not FQDNs. The c-ares resolver works OK, and it works...

More info. This is a c-core issue with the Windows native DNS resolver. I've reproduced the slow DNS lookups with a standalone C program. - Windows DNS resolver is slow...

The workarounds are to use c-ares resolver or a FQDN. Further investigation indicates that Windows is trying NetBIOS name resolution when a local name is given and this may involve...

This is the same as https://github.com/grpc/grpc/issues/30167 The problem is that Server.Start() is not called before Server.ShutdownAsync(). I'm not sure if this is API misuse issue (i.e. you must call Server.Start()...

Created PR https://github.com/grpc/grpc/pull/31232 to do what was suggested in https://github.com/grpc/grpc/issues/23390#issuecomment-1216479019

I've created a Pull Request to handle the exception in `AsyncCall.UnaryCall()`. PR https://github.com/grpc/grpc/pull/30429 Rather than just throwing the exception I have created an `RcpException` and set the exception in `unaryResponseTcs`....

There are two issues to address: - why does the decoding of the status fail? - how to handle a low level error and report the error rather than causing...

@zhenomansh thank you. Is there any chance you could modify the code for `GetReceivedStatusOnClient` to give a few more details in the exception message? Things that would be useful are:...

@zhenomansh I've created a draft PR with additional debug info in `GetReceivedStatusOnClient()` https://github.com/grpc/grpc/pull/31343 ```C# public ClientSideStatus GetReceivedStatusOnClient() { StatusCode statusCode = StatusCode.Unknown; int detailsLengthInt = -123; IntPtr detailsPtr = IntPtr.Zero;...

@zhenomansh thank you for the update. The data does look totally random - not UTF-8 or ASCII. This might be because memory is being re-used after freeing or some other...