Search Issue Tracker
Duplicate
Votes
1
Found in
2022.1.0a10
Issue ID
1367408
Regression
Yes
EditorLoop time in Profiler keeps incresing when in Play Mode
How to reproduce:
1. Create a new project
2. Open Window > Analysis > Profiler and select only the “CPU Usage” module
3. In the Profiler click the “Live” button
4. Enter the Play Mode
Expected result: EditorLoop time in the Profiler stays constant
Actual result: EditorLoop time in the Profiler keeps constantly increasing
Reproducible with: 2022.1.0a10
Not reproducible with: 2019.4.30f1, 2020.3.19f1, 2021.1.22f1, 2021.2.0b13, 2022.1.0a9
Notes:
- EditorLoop can be decreased temporarily by clicking on any intractable UI element and holding down the mouse button.
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
- 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
Resolution Note:
Fixed in 2022.1.0a11