Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2018.4.X, 2019.3.X
Votes
0
Found in
2018.3.9f1
Issue ID
1141872
Regression
No
[Player] [Profiler] Profiler keeps connecting to the same player even if it's not restarted
To reproduce:
0) Have one computer for the editor and another for the player
1) Create a new project
2) Open Build Settings, switch to second computer's platform, enable "Development Build"
3) Build it
4) Run on the second computer
5) Open up Profiler window in the editor and connect it to the player
6) Disconnect it after a few seconds
7) Disable network from one of the computers (either by pulling the ethernet cable or turning off WiFi, depending on connection)
8) After a bit of time (~15-30 seconds, to make sure that it's registered properly), reenable network
Results: Profiler reconnects to the player even though it shouldn't.
Reproduced in 2018.3.9f1, 2019.1.1f1, 2019.2.0a13
While the customer reports getting this issue constantly, internally it could only be reproduced rarely
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
Add comment