Search Issue Tracker
Fixed in 5.5.0
Votes
0
Found in
5.1.0f2
Issue ID
702370
Regression
No
OSX Standalone Player using -batchmode command line argument uses up about 70% CPU
How to reproduce:
1. Open attached project
2. Open scene main.unity
3. Build to OSX Standalone
4. Run the standalone build with the -batchmode command line argument
- Activity Monitor shows that the standalone build uses up a huge amount of CPU
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Redoing creation of Sub Scenes and Cube GameObjects in Hierarchy throws “Assertion failed on expression: 'targetScene != nullptr’” error in Console window
- Selecting “New Sub Scene” after assigning “New Scene” in Sub Scene Script Component throws “Destroying GameObjects immediately is not permitted” in the Console window
- Shader Graph "Zoom Step Size" can be set to 0 even though the zoom still works
- Enabling/Disabling the Deprecated Nodes doesn't apply to the opened Shader Graph unless any Variable is added to the Blackboard
- Group Selection title text size is smaller in renaming than the actual font size
Add comment