Search Issue Tracker
By Design
Votes
0
Found in
5.3.4p4
Issue ID
938818
Regression
No
[iOS] Memory usage between Debug Navigator and Allocation Instrument differs when instantiating objects and reloading the scene
Reproduction steps:
1. Build the attached project to iOS device.
2. Go to Debug Navigator tab in the Xcode.
3. Select Memory.
4. Press Model 1-10, press Reload (Button in the built iOS application).
Press Model 11-20, press Reload.
Press Model 21-30, press Reload.
Press Model 1-50, press Reload.
Press Model 51-100, press Reload.
5. Compare current memory usage with the starting one (Screenshot attached(Debug Navigator)).
- Current memory usage is higher.
6. Stop the application.
7. Run it again with Allocations instrument.
8. Repeat step 4.
9. Compare current memory usage with the starting one (Screenshot attached(Allocation Instrument)).
- Current memory usage is similar to the starting one.
Reproduced with:
5.2.5f1, 2017.2.0b6, 2017.3.0a3
Tested with:
iPadMini 4 10.3.2
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
- Joint Physics result in unexpected behaviors when used for articulated vehicles like buses or trucks
- Standalone Player crashes with "TDerived GetOrLoad<TDerived>() where TDerived : T" when IL2CPP Code generation is set to "Faster (smaller) Builds"
- IndexOutOfRangeException and InvalidOperationException when logging XML string
- Script missing in "Assets/Settings/Mobile_Renderer/GlobalVolumeFeature" of "com.unity.template.urp-blank" template
- “Font Asset Creator - Error Code [Invalid_File_Structure]…“ error is logged when generating Font Assets from fonts which worked with TMP Font Asset Creator
Resolution Note:
This is not a bug. Xcode’s memory report is good for noticing memory usage trends. But it is not very accurate tool. Please check this thread https://forums.developer.apple.com/thread/52186
And in any case this cannot be Unity specific problem.