Search Issue Tracker
Fixed in 2021.2.X
Votes
0
Found in
2020.3
2021.1
2021.2
2021.2.0a18
Issue ID
1337020
Regression
No
Incorrect "Main Thread" marker time reported to ProfilerRecorder whilst Profiler is recording
How to reproduce:
1. Open attached project "New Unity Project.zip"
2. Open "SampleScene" scene
3. Open Profiler window & disable Profiler recording
4. Enter Playmode
5. Observe the "Main Thread" time values being logged to the console
6. Enable the Profiler recording
7. Observe the "Main Thread" time values being logged to the console
Expected result: "Main Thread" values after enabling Profiler recording do not not change drastically
Actual result: "Main Thread" values after enabling Profiler recording become way smaller
Reproducible with - 2020.3.9f1, 2021.1.8f1, 2021.2.0a18
Not reproducible with (errors) - 2018.4, 2019.4
Notes:
Cross reference these values with the CPU Time shown in the Profiler window and it appears that these tiny values are incorrect
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 (fix version 2021.2):
Fixed in 2022.1.0a2