Search Issue Tracker
By Design
Votes
0
Found in
2021.3.51f1
2022.3.61f1
6000.0.48f1
6000.1.1f1
6000.2.0a10
Issue ID
UUM-104080
Regression
No
Connection to Named Pipes fails when server and client are run
Reproduction steps:
1. Open the attached “IN-99790/Source/Client” project
2. Open the Build Settings window (File > Build Settings)
3. Build the Project
4. Launch the “IN-99790/Builds/Server/LinuxNamedPipeTest” executable through the terminal
5. Launch the Build through the terminal with {{-logFile {path}}} argument
6. Observe the terminal and log file outputs
Expected result: Both Server and Client successfully connect to the two named pipes and each sends and receives a single message without issue
Actual result: Neither Server nor Client successfully completes the connection to the named pipes because the Unity side has the issue where it is blocked.
Reproducible with: 2021.2.0a18, 2021.3.51f1, 2022.3.61f1, 6000.0.48f1, 6000.1.1f1, 6000.2.0a10
Not reproducible with: 2021.2.0a17
Reproducible on: Ubuntu 24.04
Not reproducible on: No other environments tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Test Runner’s vertical scrollbar overlaps with the up and down arrows and upper toolbar tabs when the window is minimized
- The Input Field view is not updated when deleting lines of text
- The scrollbar does not respect empty lines in the Input Field
- “Texture Atlas Viewer“ button text overlaps another button when the UI Toolkit Debugger is narrowed
- Thresholds are no longer automatically calculated after deleting Motion fields in Blendtrees
Resolution Note:
The named pipe support is the class libraries was changed from using the underlying OS's named pipe support to using Unix domain sockets. This is not a change we plan on reverting.
To work around this P/Invoke into the OS's mkfifo API to create a named pipe.
See https://github.com/dotnet/corefx/pull/6833 for details on the change.