Search Issue Tracker
Fixed in 5.6.0
Votes
0
Found in
5.6.0b3
Issue ID
866930
Regression
Yes
Clicking on profiler while standalone player is being profiled might cause profiler to disconnect from it
Steps to reproduce:
1. Create new project
2. Build and run standalone as development build (run it as windowed for an easier repro)
3. Back in editor, connect profiler to the build
4. Click back on build to confirm that profiler got connected
5. Click back on profiler and sometimes you'll get an indication of something loading and after that profiler will get disconnected
So far, the best way to repro this is by enabling/disabling profiler options (Scripts, Rendering, GarbageCollector etc.)
Tested on OSX
Reproduced with: 5.4.0p4, 5.4.4f1, 5.5.0f3, 5.5.0p3, 5.6.0b3
Not reproducible: 5.3.7p3
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- GameObjects change Hierarchy order when undoing adding Component to multiple GameObjects
- [macOS] Editor crashes after entering Play mode with overlapping GameObjects with Cloth Component and Cloth Inter-Collision enabled
- Look Dev constantly regenerates the default Volume Profile when set to "None" instead of using the default one
- Look Dev errors are spammed when opening a new HDRP project when Look Dev was added to the layout in the previous project
- URP Scene Templates are not editable when first opened from the New Scene dialog
Add comment