Search Issue Tracker
By Design
By Design in 6000.2.X
Votes
0
Found in
2021.3.38f1
2022.3.27f1
6000.0.0b16
6000.1.0a3
6000.2.0a1
Issue ID
UUM-9437
Regression
No
Video Player continuously allocates IOSurface buffers when rendering to Render Texture until device runs out of memory and crashes
How to reproduce:
1. Open the attached project ("VP Test.zip")
2. Build an Xcode project (iOS, macOS)
3. Deploy to a device
4. Profile in Instruments to observe memory allocations
Reproducible with: 2020.3.37f1, 2021.3.6f1, 2022.1.10f1, 2022.2.0b2, 2023.1.0a4
Reproducible on:
iPhone 13 mini (iOS 16 public beta 1)
iPad 6th gen (iOS 14.4.2)
macOS 12.4 (Intel) - did not crash but memory usage did continue to increase
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
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
- Changing Transform values in Search window Inspector loses focus while dragging and stopping mouse without releasing dragging action
- Saving changes on the dirty VFX Graph during the Play mode throws "The referenced script (Unknown) on this Behaviour is missing!" warnings
- VFX Graph Debug Info overlaps the "Initialize" block debug info by default
Resolution Note:
The VideoPlayer buffers between 8 and 11 decompressed frames via IOSurfaces provided by AVFoundation's decoding. Playing more than one 4K clip on an iPad Air 2 therefore goes above the memory usage threshold for this device, so using lower resolution clips - e.g. matching the device's screen resolution of 2K - would be a safer approach.
Resolution Note (6000.2.X):
The VideoPlayer buffers between 8 and 11 decompressed frames via IOSurfaces provided by AVFoundation's decoding. Playing more than one 4K clip on an iPad Air 2 therefore goes above the memory usage threshold for this device, so using lower resolution clips - e.g. matching the device's screen resolution of 2K - would be a safer approach.