Search Issue Tracker
Fixed in 2019.4.X
Votes
22
Found in
2017.1.1p4
Issue ID
998484
Regression
No
Different, not-consistent threads count in standalone builds
To reproduce:
1) Open attached project and scene
2) Build and run it
3) Use some tool to check thread count (Process Explorer on win, command "cat /proc/%PROCESS_ID%/status" on Linux)
Expected: Thread count is kept the same
Actual: Thread count differs on each build
Tested on a machine which has both Linux and Windows
Reproduced in Win: 2017.1.0f3 (65 threads), 2017.3.1p1 (64), 2018.1.0b7 (61)
Reproduced in Linux 2018.1.0p2 (47)
Comments (1)
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
Sliem001
Sep 09, 2020 08:04
Unity 2020.2.0b1 Beta
Problem still exists.