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
- Assets are created in the Package folders when creating assets via custom buttons in the Inspector window or other windows
- “Select” windows are named differently on Windows and macOS
- [Windows] No minimum “Select” window size
- Enabling “Editor Extension Authoring” in UI Builder doesn’t dirty the document and saving with shortcut doesn’t persist the state
- WebRequest.Create() function fails with "URI prefix is not recognized" errors when the project is built for Linux Standalone or Windows Dedicated Server
Add comment