Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2020.1.X
Votes
0
Found in
2020.1.0a23
Issue ID
1219310
Regression
No
[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:
2020.1.0a23
Working Fine on:
2020.1.0a22, 2020.1.0a21
Note:
Standalone Profiler was introduced in 2020.1.0a21
Environment:
Windows 10 and macOS 10.14, 10.15
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Add comment