Search Issue Tracker
Not Reproducible
Votes
0
Found in
5.5.1p4
Issue ID
895347
Regression
No
"Unaccounted time between" spikes in CPU usage when selecting objects in Hierarchy
Lots of "Unaccounted time between" processor load when the project is simply running in play mode.
Steps to reproduce:
1. Open provided project
2. Select any item in the Hierarchy (Might just start on its own, without selecting anything)
3. Observe the profiler (There should be spikes in CPU usage on a constant flow)
Expected outcome: No irregularity in the CPU load.
Actual outcome: Steady stream of spikes of "Unaccounted time between" blocks
Tested on 5.5.1p4 and 2017.1.0a4
Notes: Though when starting out it was just solitary spikes in CPU load instead of a steady stream. Not sure what changed.
Notes: Unable to reproduce on multiple machines and versions anymore
Comments (4)
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
realprimo
Sep 22, 2019 22:14
still......
Black_Raptor
Dec 25, 2017 21:27
Still have ! With empty scene ...
numberkruncher
Dec 06, 2017 00:23
+1 same issue.
jackaperkins
Oct 07, 2017 14:30
Getting this also, in a scene with minimal rendering and scripts. Total Camera.render is 0.54ms on 2015 macbook, Unaccounted time spikes Upwards of ~40.0ms