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
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
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