Search Issue Tracker
Won't Fix
Votes
0
Found in
5.6.0b8
Issue ID
880628
Regression
No
[iOS] 'VM: Performance tool data' leak with all projects on iOS 10.3 when build is running in Xcode
When an empty Unity build is running on iOS 10.3 device, with Xcode attached, memory is continuously leaked by 'VM: Performance tool data'.
Steps to reproduce:
1) Create a new project.
2) Build for iOS.
3) Run on iOS 10.3 device via Xcode.
- The memory consumption can already be seen in Debug section of Xcode.
4) Transfer the build to Instruments.
Notice the memory usage growth in 'VM: Performance tool data'. 544/32 kB are allocated repeatedly. libBacktraceRecording.dylib is responsible for the calls. If the app is launched from Instruments directly, the leak doesn't occur.
Reproduced on:
5.6.0b8, 5.6.0b3, 5.5.1p4
Did not reproduce 5.4.4p3
Devices:
iPhone 6S iOS 10.3
iPhone 7 iOS 10.3 - reproduced
iPhone 5S iOS 9.3.3 - did not reproduce
iPhone 5 iOS 10.1 - did not reproduce
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unused separation line is used in the Prefab Context Menu when right clicking child Prefabs
- Editor freezes indefinitely when copy pasting a lot of characters in the UI Builder’s “Add new selector” field
- Detached Audio Source is not released from browser memory when Audio stops playing in WebGL Player
- "Canvas.pixelRect" and "Canvas.renderingDisplaySize" report 640x480 when Device Simulator window is unfocused after reopening the project in the Editor
- Incorrect indices when using Graphics.RenderPrimitivesIndexedArgs[] with Graphics.RenderPrimitivesIndexedIndirect
Add comment