Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
0
Found in
2017.4
2019.3.6f1
2020.2
Issue ID
1238290
Regression
No
[Build] Unity only checks for one socket when detecting CPU count
This is an ES bug reported by Google.
How to reproduce:
1. Create new project
2. Open Task Manager
3. Observe Unity Editor task CPU usage
4. In Editor, File -> Build & Run
5. Observe Unity Editor task CPU usage
Expected result: all CPU cores are active during the standalone build process
Actual result: only one CPU has its cores maxed out
Reproducible with: 2017.4.40f1, 2018.4.22f1, 2019.3.12f1, 2020.1.0b8, 2020.2.0a9
-
JoyWayUnity
Jun 29, 2022 07:47
In version 20.3.20f1 when building the project. I see the use of only 1 CPU.
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
- Missing Device Simulator API
- Shadow gets cut off when in Play Mode and using shader "Shader Graph/Rotation Shader" for material
- Unable to get textureOverrideSettings from BuildPipeline.GetBuildTargetName when trying to pass in the platform string
- Getting the current process name returns Null when building with IL2CPP
- Documentation page is not displayed for the user when he clicks on "Open Reference for SceneTemplateAsset" question mark
Resolution Note (fix version 2020.2):
Verified in:
Version: 2020.2.0a12
Resolution Note (fix version 2020.1):
Fixed in:
Version: 2020.1.0b15
Resolution Note (fix version 2019.4):
Fixed in:
2019.4.5f1