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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment