Search Issue Tracker
Fixed
Votes
0
Found in
2019.4
2020.1.6f1
2020.2
Issue ID
1294973
Regression
No
Threads perform at vastly different speeds when performing nearly identical calculations
Reproduction steps:
1. Open user attached Project
2. Open "Assets\Scenes\ThreadTest"
3. Press Play
4. Press Start
Expected result: Threads spend relatively the same time
Actual result: The time spent calculating has a difference factor of around 4-5
Reproducible with: 2019.4.11f1, 2020.2.0b13
Not reproducible with: 2019.4.12f1, 2019.4.18f1, 2020.2.0b14, 2020.2.2f1, 2021.1.0b3, 2021.2.0a2
Could not test with: 2018.4 (Project breaks)
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 2020.2.0b14 and 2019.4.12f1