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
- When the registry value for "TimeZoneKeyName" is invalid, "TimeZoneNotFoundException" exceptions are thrown
- [2018.4] UnityWebRequest.java has a sHostnameVerifier which doesn't have server identity check implemented
- Secondary hidden Hierarchy windows pop up when a new gameObject is created in another Hierarchy window
- UI Details profiler does not display any information when selected and throws exceptions when UI module is disabled
- [UWP] ContentDialog box doesn't disable apps interactivity
Add comment