Search Issue Tracker
By Design
Votes
0
Found in
5.4.3f1
Issue ID
859305
Regression
No
[iOS] Unity's profiler device memory consumption is different from consumption shown by XCode
Steps to reproduce:
1. Create a new Unity project
2. Build to iOS with "Development mode" and "Autoconnect profiler"
3. Open the project with Xcode
4. Build & Run on an iOS device
5. In Unity, attach the profiler to the running app
6. Check the memory consumption shown on profiler
7. Check memory consumption in Xcode's Debug Navigator
Expected results: memory consumption is the same in both tools
Actual results: Unity profiler shows a lower number (~20MB) compared to Xcode's Debug Navigator (~30MB)
Reproduced on: 5.5.4p1, 5.6.2f1, 2017.1.0f1, 2017.2.0b1
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
- “GUIStyle” and “NullReferenceException” errors thrown in the Console when opening Object Field during script compilation
- Reflections are visible on objects without Recursive Rendering when viewed through transparent parts of another object with Recursive Rendering and Alpha Clipping enabled
- Visual artifacts appear when using "clip" method in custom shader and running on GLES
- Scaled Backgrounds List and dropdown text are enabled while Scaled Backgrounds field is disabled in IMGUI Debugger window
- Editor crashes when large value is entered in Scaled Backgrounds field of IMGUI Debugger window
Resolution Note (2020.1.X):
Unity Profiler's Total Reserved (and Used) Memory shows memory usage information which Unity counts.
Memory usage in XCode can be higher or lower depending on resident/paged situation and how many allocations came from native plugins.
The Total System Used Memory being 0 in the thread is a bug. It has been fixed separately to report resident size and is being backported.