Jonathan Chambers
Jonathan Chambers
Debugging a bit locally, and I see the call [here ](https://github.com/dotnet/runtime/blob/main/src/libraries/System.IO.Pipes/src/System/IO/Pipes/NamedPipeClientStream.Windows.cs#L47) to `CreateNamedPipeClient` repeatedly fail and return `Interop.Errors.ERROR_FILE_NOT_FOUND`
The value of `_normalizedPipePath` is `\\.\pipe\A3e62qkUmq+JJ8FWJ7uk5QQGtvwg_ahrh712xdcr_sc`
After debugging a bit more, it seems like the issue is that we are using a zip/binary deployment of the SDK. We do not have 8.0.200 installed on the machine....
Hello @bluerise wondering if you hit any issues related to this in Unity? I'm wondering about the motivation for the PR to our fork? Thanks!
Hello @devnexen. I talked to our platform team. It seems the `fp` register is already aliased to `x29` register, so this should be causing issues. I was wondering if you...
I think we see this in Unity too. Assemblies not being unloaded during app domain unload. It seems related to incorrect image/asssembly ref counts.