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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Add comment