Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.2.X, 2017.3.X, 2018.1.X
Votes
0
Found in
2017.1.0f2
Issue ID
929984
Regression
No
Crash when implementing asynchronously named pipes in Mono/C
Reproduction Steps:
In Visual Studio:
1. Unzin the source.zip file.
2. Open the project file with VS. It contains 3 projects (server, client, MessageBusLib).
3. Set the "Server" project as the StartUp project.
4. Press Start, it should open a cmd console for the server waiting for a client.
Unity Side:
1. Import attached project from "929984 - AsynchronousPipes.zip".
2. Open "LevelEditor" scene.
3. Enter Play mode.
Result: Unity crashes.
Reproducible with: 5.6.2p3, 2017.1.0f3, 2017.2.0b1
Fixed in - 2018.2.0a1, 2018.1.0b9, 2017.3.1p2, 2017.2.2p1
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Frame Debugger is not disabled when switching Scenes if the Frame Debugger window is not open during the transition
- Standalone Profiler Targets another Project if a Standalone Profiler was launched in it before when switching between Edit or Play Mode Targets
- Crash on ForwardRenderLoopJob when opening a specific project
- [Android] Memory leak and eventual crash on Snapdragon 8 Gen 1+ devices when a Clear Pass is executed after Framebuffer Fetch
- PhysicsRaycaster ray length is incorrect when casting from rotated Camera
Add comment