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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
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.