Search Issue Tracker
By Design
Votes
0
Found in
2017.4
2018.4
2019.3
2020.1
2020.2
2020.2.0a9
Issue ID
1241102
Regression
No
[Frame Debugger] Enabling Frame Debugger interrupts Profiler recording when Targetmode is set to Player
Steps to Reproduce:
1. Create a New Project
2. Edit > Build Settings > Dev Build+AutoConnect Profiler > Enable
3. Build and Run
4. Window > Analysis > Frame Debugger > Target: Player(if not already)
5. Frame Debugger > Enable
Actual Results:
1. Profiler recording is paused as long as frame debugger is enabled
2. Enable button doesn't update to "Disable"
Expected Result:
1.Profiler should run uninterrupted as it does when both are Targetting Editor.
2.Enable button should update to "Disable"
Reproducible with: 2020.2.0a9, 2020.1.0b8, 2019.3.10f1, 2018.4.19f1, 2017.4.34f1
Note:
For 'Playmode', Profiler gets paused(if it is targetting Playmode) as the Play is paused by enabling Frame Debugger(as it targets editor). But when both are connected to a Player after 'Build and Run' the Play does not pause and hence the Profiler shouldn't either.
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
- Misaligned text in Preferences window > 2D > Animation, Asperite and Sprite Editor preferences
- Unable to Install ZivaRT Player deprecated package
- Inconsistent Label Popup UI in Package Manager
- All active Audio Sources play their Clips when the "Play On Awake" checkbox is enabled and Scene view Audio is unmuted
- Crash on RuntimeFieldInfo::ResolveType with IL2CPP and returns 0 with Mono when calling GC.GetAllocatedBytesForCurrentThread Method
Resolution Note:
By-design because the behavior is correct.
Profiler recording is paused as long as frame debugger is enabled <- the actual result is the correct behavior and same as editor playmode.
Enable button is a toggle so it doesn't need to be changed to disable. Behaviour with targeting player / editor is same so nothing is wrong.