Search Issue Tracker
Fixed in 5.3.7
Votes
5
Found in
5.3.5f1
Issue ID
800209
Regression
No
[tvOS] Memory usage is consistently increasing in a tvOS build
Steps to reproduce:
1. Open attached project
2. Build for tvOS
3. Build generated Xcode project to Apple TV
4. Keep the project running for a while and look at the apps memory report in Xcode
5. Notice the memory usage is increasing all the time
RESOLUTION:
It looks like the apparent memory leak is caused by two things:
1. "Enable backtrace recording" setting being checked in the run scheme options. This is what causes the runaway memory usage.
2. 8MB virtual memory block taken by libc malloc at the startup of the application being slowly dirtied due to fragmentation. To Xcode it looks like increased memory usage. While it indeed increases memory pressure slightly, it is pretty much expected.
Both of the above do not happen on older tvOS versions, so we think that the some internal changes in tvOS itself are to blame.
We will set the "Enable backtrace recording" setting in the default run schemes provided by Unity to unchecked.
As for the 8MB allocation, there's not much we can do about it. The only fix is to significantly reduce the number of transient memory allocations, which needs a large refactor of the Unity core.
Comments (3)
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
- Mono Windows Builds don't produce full log callstacks when generating logs
- AssetBundles fail to load when running in Built Players for Mobile Devices
- UI elements with text gets bigger and grey when Player window is moved to another screen with different resolution
- System name accepts multiline text but crops it on confirmation, duplicates input, and shrinks the field when empty
- UI element scale and position are wrong in project build when DRS is changed with HDR and Software Dynamic Resolution enabled
Rude Bob
Jun 28, 2016 13:10
Great advice! Problem is solved! Thanks a lot LIMIVOROUS!!!!!
limivorous
Jun 27, 2016 11:33
Try disabling backtrace recording in the scheme editor.
Solved it for me!
tato23
Jun 24, 2016 03:56
Yeah! Anyone solved??