Search Issue Tracker
Fixed in 2021.1.X
Fixed in 2020.2.X
Votes
0
Found in
2020.1
2020.2.0b11
2021.1
Issue ID
1293059
Regression
Yes
The Profiler updates all modules when only one module is enabled
How to reproduce:
1. Create a new project
2. Open Window > Analysis > Profiler
3. Disable all modules except the CPU Usage module
4. Enable 'Deep Profile'
5. Change the profiling target to 'Editor'
6. Capture some data
7. In the Module details panel set the view option to 'Hierarchy'
8. In the search bar enter 'ProfilerModuleBase.Update()'
9. Observe the 'Calls' value of 'ProfilerModuleBase.Update()'
Expected result: The 'Calls' value is equal to 1
Actual result: The 'Calls' value is equal to 14
Reproducible with: 2020.1.14f1, 2020.2.0b12, 2021.1.0a6
Cannot test with: 2018.4.29f1, 2019.4.15f1 (ProfilerModuleBase.Update() does not occur)
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
- Crash on JobQueue::HasJobGroupIDCompleted when closing the Editor while in Play mode on a specific project
- In "Preferences" section the “SpriteShape” menu item, the details page title “SpriteShape”, and “ControlPoint” entries are displayed as code strings rather than formatted UI strings
- Errors thrown constantly when Virtual Offset Debug is enabled and lighting was baked on AMD machine
- Persistent Memory Leak when reloading domain and using Distance-based Ghost Importance
- HDRP project doesn't render in standalone player when using High stripping
Resolution Note (fix version 2021.1):
Fixed in 2021.2.0a2
Resolution Note (fix version 2021.1):
Fixed in 2021.1.0b3
Resolution Note (fix version 2020.2):
Fixed in 2020.2.3f1