Search Issue Tracker
Won't Fix
Votes
1
Found in
Issue ID
1106575
Regression
Yes
[iOS] Memory usage increased 8-10% from 2017.4 to 2018.2
While testing with the project from https://fogbugz.unity3d.com/f/cases/1100123/ I noticed that memory usage appears to have increased a significant amount in 2018.2. Here are the testing results using the MemTest project attached to the other bug. The point of that test is to see how many meshes can be created before being terminated due to memory pressure.
The target OS does not appear to matter and it seems to vary a little between devices but the increase is there nonetheless.
iPad Air 2 iOS 11.4.1
Unity 2017.4.16f1
405k meshes before being terminated due to the memory limit
Unity 2018.2.18f1
363k meshes before being terminated due to the memory limit
iPhone 6s Plus iOS 12.1
Unity 2017.4.16f1
378k meshes before hitting the 1400MB limit
Unity 2018.2.18f1
349k meshes before hitting the 1400MB limit
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
- [Mobile] Developer Console does not appear when an error is thrown
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (2018.2.X):
Lukas has a good point. This was resolved in 2018.3 and 2018.2 is no longer being updated.