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
- [Hub][Linux] Hub .AppImage does not allow to upgrade the Hub from 2.4.5 to 3.0.0-beta.2
- [Profiler] Current frame button initially hides profile frame marker
- Missing function to reset or unset a specific resource in the local binding space of compute shaders
- [Linux][Hub] Unity Hub 2.4.5 does not open "Add modules" window when clicking "Install with Unity Hub" in Build Settings
- Multiple errors appear in the Console when building for IL2CPP
Add comment