Search Issue Tracker

Fixed in 2020.2.X

Fixed in 2020.1.X



Found in


Issue ID




[Profiler Standalone] Profiler stops profiling and throws NullReference Errors on changing Profiler Mode from Playmode to Editor



On changing the 'Target Selection' in the Standalone Profiler from the default 'Playmode' to 'Editor' stops data profiling, throws continuous Null Reference Exceptions and also leads to the Menu Bar flickering constantly.
Refer to the attached video.

Steps to Reproduce:
1. Create a New Project
2. Window > Analysis > Standalone Profiler
3. Enter and exit Play mode (Observe that errors are thrown but they stop after exiting Play mode)
4. Change profiler mode to Editor (Observe continuous errors that don't stop)
5. Change profiler mode back to Playmode
6. Enter Play mode again

Actual Result:
Continuous Null Reference Exceptions are spammed in the console and the profiler stops profiling for 'Playmode' and continues for 'Editor'.

Expected Result:
Profiler profiles Editor Data and Playmode data according to the 'Target' selected.

Occurring on:

Working Fine on:
2020.1.0a22, 2020.1.0a21

Standalone Profiler was introduced in 2020.1.0a21

Windows 10 and macOS 10.14, 10.15

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.