Search Issue Tracker
Duplicate
Votes
0
Found in
2020.2.0a2
2021.1
2021.1.0a7
Issue ID
1297200
Regression
Yes
[Profiler] "Connection is no longer valid" is thrown when switching Profiler Target from Player to any other
How to reproduce:
1. Create a new Unity project
2. Open the Build Settings (File->Build Settings...)
3. In the Build Settings window enable "Development Build" and "Autoconnect Profiler" options
4. Build And Run the project
5. Once the Build is open switch to the Editor
6. In the Profiler window switch the Target to the Editor (switching to Player also produces the same issue)
7. Switch back to the Build
Expected results: No errors are thrown in the Development Build Console
Actual results: The "Connection is no longer valid. Calling auto disconnect." error is thrown in the Development Build Console
Reproducible with: 2020.2.0a2, 2021.1.0a9
Not reproducible with: 2018.4.30f1, 2019.4.16f1, 2020.1.17f1, 2020.2.0a1
Notes:
- The issue has been tested and reproduced on Windows
-
fedorpm
Mar 19, 2021 09:36
But it isn't duplicate issue. Issue under link not reproduced in my case with Unity 2020.3.0f1, but with profiler it is.
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
- Fixing Message Loss in UMPE During Domain Reload
- The Editor freezes when ScheduleReadOnly of IJobParallelForTransform with dependency is used
- Text is truncated in the Inspector when the display scale is set to 150%
- CancellationTokenSource(<timeout>) has incorrect cancellation status when used in WebGL Player
- VFX property value names are cut off when properties with 'Arc' are viewed in the VFX Blackboard
This is a duplicate of issue #1259522