Search Issue Tracker
Fixed in 2017.1.X
Votes
0
Found in
5.5.0b2
Issue ID
827826
Regression
No
[Networking] [Profiler] Editor Crash on closing standalone Player with active Profiler session
Crash happened only twice.
1. Run Standalone as Host.
2. Run in Editor as Client.
3. Run Profiler - Set Active profiler as OSXPlayer).
4. Close Standalone.
5. Return to Unity.
6. Press on Profiler - Select OSXPlayer in Active Profiler.
Actual result: Unity crashes or throws errors:
Socket: connect failed, error: Connection refused(61)
UnityEditorInternal.ProfilerDriver:set_connectedProfiler(Int32)
UnityEditor.AttachProfilerUI:SelectProfilerClick(Object, String[], Int32)
connect failed
UnityEditorInternal.ProfilerDriver:set_connectedProfiler(Int32)
UnityEditor.AttachProfilerUI:SelectProfilerClick(Object, String[], Int32)
Failed to connect to player ip: 172.31.26.46, port: 55147
UnityEditorInternal.ProfilerDriver:set_connectedProfiler(Int32)
UnityEditor.AttachProfilerUI:SelectProfilerClick(Object, String[], Int32)
Expected result: Unity does not crash.
Reproduced on 5.5.0b2.
Does not reproduced in 5.4.0f1.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Add comment