Search Issue Tracker
Fixed in 2018.2.X
Votes
0
Found in
2017.3.0p2
2017.3.0a5
Issue ID
990825
Regression
Yes
[iOS] Performance regression on iOS introduced in 2017.3.0 alpha
Reproduction Steps:
1. Open User's project
2. Build for iOS (development build)
3. Deploy to an iOS device
4. Attach Unity profiler
5. Notice the difference in CPU usage
Approximate test results:
Unity 2017.1.3f1 - CPU ~2.3 ms
Unity 2017.2.1p4 - CPU ~2.3 ms
Unity 2017.3.0a1 - CPU ~6.8 ms
Unity 2017.3.0a4 - CPU ~6.5 ms
Unity 2017.3.0a5 - CPU ~33.3 ms
Unity 2017.3.0p3 - CPU ~33.3 ms
Unity 2018.1.0b4 - CPU ~33.2 ms
Expected Behaviour: Similar CPU/GPU with different Unity versions.
Good performance: Unity 2017.1.3f1, 2017.2.1p4
Worse performance: Unity 2017.3.0a1, 2017.3.0a4
Current performance: Unity 2017.3.0a5, 2017.3.0p4, 2018.1.0b4
Reproduced on device: iPhone 7 Plus iOS 10.3.2
Comments (1)
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
- Errors are logged when importing an asset at a path with Firebase
- Entering too big of a number in 2D Renderer Lightmode Tags freezes the Editor
- Crash on GUIManager::DoGUIEvent when focusing on the Game view window on a specific project
- Asset creation in the Project Browser is not always undone/inconsistent when the undo shortcut is pressed right after creating an asset
- JobTempAlloc memory leak warning is thrown when the Player is shut down
PolyVector
May 23, 2018 18:34
Any chance this will be resolved in the LTS stream? This bug is driving me absolutely crazy.