Search Issue Tracker
Duplicate
Votes
0
Found in
2019.4
2019.4.20f1
2020.3
2021.1
Issue ID
1322863
Regression
No
VideoPlayer leaks memory when frame is set to 0 before playing in Play Mode
How to reproduce:
1. Open attached project "VideoPlayerMemoryLeak.zip"
2. Open "memoryLeak" scene
3. Enter Play Mode
4. Open Task Manager and observe memory section
5. In the Editor, press spacebar multiple times (at least 10 times) to restart the video
Expected result: Memory usage is not increased
Actual result: Memory usage keeps increasing until the editor crashes
Reproducible with - 2019.4.25f1, 2020.3.5f1, 2021.1.5f1, 2021.2.0a4
Not reproducible with - 2021.2.0a5, 2021.2.0a15
Could not test - 2018.4 (errors)
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
- var VisionOSEDRHeadromm has a comma instead of a dot when building with Metal Rendering App Mode and local OS localization is set to German
- IAP Catalog remove product “x” and add product “+” buttons are not consistent with other remove and add buttons in the Editor
- Performance issues in Play Mode when quickly hovering the mouse cursor over Hierarchy GameObjects
- Frame Debugger displays incorrect output when FidelityFX Super Resolution or Spatial-Temporal Upscaler is used with Temporal Anti-aliasing or Subpixel Morphological Anti-aliasing
- Crash with “Fatal Error! The file ‘MemoryStream’ is corrupted!” when adding a large number in Font Character Rects Size field
Resolution Note:
The leak is not due to the frame being set to 0 before playing. It's due to the fact that the video playback is stopped while a seek is ongoing (VideoPlayer.frame = 0 and VideoPlayer.Stop() in rapid succession). This is addressed by the fix for 1308317.