Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.3.0b5
Issue ID
1090530
Regression
No
[iOS] Device SDK reports more memory usage in Xcode than Simulator SDK
1. Open attached project "testcase.zip"
2. Build for iOS "Device SDK"
3. Deploy the Xcode project to the iOS device
4. Observe Memory usage in "Show the Debug Navigator" tab
5. Memory usage is about 1.35gb
6. Build the project to iOS "Simulator SDK"
7. Open the Xcode project and run it on iPhone XS Max
8. Observe the memory usage
9. Memory usage is about 600MB
Expected result: memory usage is similar between the simulator and device SDK
Actual result: memory usage is different between the simulator and device SDK
Reproduced on:
2017.4.0f1 2017.4.17f1 2018.2.20f1 2018.3.0b5 2018.3.1f1 2019.1.0a12
Devices tested on:
iPhone XS Max iOS 12.0
iPhone 7 Plus iOS 12.0
Notes:
Tested on iMac MacOS version 10.14 when deployed to a device , it only shows a black screen and barely visible Unity logo, as it stuck on the last frame of the splash screen.
Tested on Metal and OpenGLES3 and OpenGLES2
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
- Isometric Tilemap incorrectly sorts Tiles when Sort Order is set to "Bottom Right" or "Top Left"
- [WebGL] Audio track with a loop point defined plays from the start when looping
- [Android] Semaphore.WaitForSignal causes ~200ms stalls when Dithering Node in a ShaderGraph is enabled on Samsung J7
- "Branch Group" tools have missing tooltips
- ExecuteMethod uses cached data when running validations after a CI checkout
Resolution Note:
Some difference in reported memory between the Simulator and device is expected. They are running on different CPU architecture, the simulator does not support Metal, Xcode might be tracking memory differently etc. It would be interesting to see instrument memory alloc tool traces for both platforms and the same app, though.