Search Issue Tracker
Fixed in 2020.1
Fixed in 2018.4, 2019.2, 2019.3
Votes
1
Found in
2018.1.0b9
Issue ID
1008321
Regression
No
Editor freezes if Profiler is unable to connect to Player
How to reproduce:
1. Create a new Unity project
2. Go to Window --> Profiler
3. Click on "Editor" drop down menu (in the Profiler)
4. Click on <Enter IP>, enter some invalid IP and press Connect, observe the Profiler displays "unable to connect", but the entire editor does not respond anymore.
Expected result: Editor does not freeze while connecting and attempted connection can be aborted
Actual result: Editor freezes while connecting and connection to player cannot be aborted until the connection request is failed
Reproducible with - 2018.2.0a2, 2018.1.0b10, 2017.3.1p3, 2017.2.0a1
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
- [Linux] Unity licensing command on Linux pops a progress bar when using -batchmode and -nographics
- SerializedReference GameObject property gets set to null after entering Play mode
- Profiler - RawFrameDataIterator ThreadID will always return 0 for profiler frame data loaded from .data files
- Crash on scripting_field_get_type when a Script has List<> of LayoutKind.Explicit struct with [FieldOffset(1)] ScriptableObject
- Frame Debugger doesn't work when using Camera.SetTargetBuffers
alexeyzakharov
Oct 18, 2019 12:10
I'm adding progress bar which displays the scanning progress and allows to cancel the connection attempt.