Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.2.X, 2019.3.X
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
- Crash on ShaderLab::ShaderState::ApplyShaderState when entering Play Mode and calling ShaderWarmup.WarmupShaderFromCollection with a shader that has dynamic_branch
- Crash on operator delete[] when a serializable structure in the System namespace is serialized by a MonoBehaviour
- [macOS] forward and backward mouse buttons are recognized as middle mouse button
- NavMeshModifier.OnEnable/OnDisable gets progressively slower when called repeatedly
- "System.Net.CookieContainer" throws an "ArgumentException" error when using a non-UTF-8 machine locale and hostname
alexeyzakharov
Oct 18, 2019 12:10
I'm adding progress bar which displays the scanning progress and allows to cancel the connection attempt.