Search Issue Tracker

By Design



Found in


Issue ID




[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

  1. 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
    And in any case this cannot be Unity specific problem.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.