Bug Video Player Memory Leak

The Video Player seems to have a memory leak when playing videos from an Url. Each time I load a new clip, the Memory Profiler shows an additional WindowsVideoMedia_DecodeTexture that never gets destroyed. This happens even if I just alternate between two different videos (both are loaded from my harddrive).

It happens both in the Editor and in a build. In the Editor textures persist in memory when exiting playmode.

Interestingly, the increase in memory usage the Windows Task Manager reports, is more than 10 times the size of that texture.

After a couple of video loads, the Editor first stops playing the video's audio track and then stops loading the video altogether. It logs the following error message:

Code (CSharp):

1. WindowsVideoMedia error 0x8007000e while reading C:\Path\To\Video.mp4
2.  
3. Context: IMFSourceReader::WaitForSample in StepAllStreams
4. Error details: Ran out of memory
5.  
6. Track types:
7.    Unreadable Track

 

If I only play one video, the texture gets deleted properly, but if I play a second one, the first one persists. If I alternate between these two videos, they create more of these textures, until it stops loading the videos. When I exit playmode, the last one will be cleaned up.

In the project I use APIOnly and display the texture on a RawImage. I am not sure if it happens with preloaded clips, too, I load the videos via Url.

I had it in 2020.3.12f1 and also in 2020.3.14f1

As a side note: Each of these textures produce an error message ("No texture data available to upload") when I switch the target platform.

 

Case ID is 1351889.

I have one Videoplayer.
I load one video from an Url and play it. At some point in the future, I play another video. The first video may or may not have been played till the end, but in any case I call

VideoPlayer.Stop()

before starting the new one.

Relevant code:

Code (CSharp):

1.  
2.  
3. VideoPlayer _videoPlayer;
4.  
5. void Awake() {
6.     _videoPlayer = GetComponent<VideoPlayer>();
7.     _videoPlayer.prepareCompleted += StartPlay;
8. }
9.  
10. public override void Play(string path) {  
11.     _videoPlayer.Stop();              
12.     _videoPlayer.source = UnityEngine.Video.VideoSource.Url;
13.     _videoPlayer.url = path;
14.  
15.     _videoPlayer.Prepare();
16. }
17.  
18. private void StartPlay(VideoPlayer vp) {
19.     _videoPlayer.Play();
20. }
21.  

 

After further testing (mainly trying to reproduce it in a minimal project) it seems like the culprit is setting the VideoPlayer's

frame

property to 0 before loading the next video. If I don't do that, it doesn't leak. For now I can circumvent the issue that way.

 

Here is the reproduction project.

It has only one scene and one script. When you start Play in the scene, it gets the files in the "Videos" folder and each time the "Create Leak" button is pressed, it tries to load it into the VideoPlayer and create another WindowsVideoMedia_DecodeTexture. I have included one of my test videos in the folder, so it should be testable as is, but if you want to test if it only happens with certain videos, you can just put other videos in that folder..

You can see these Textures using the Memory Profiler in Detailed mode when you navigate to "Not Saved" > "Texture2D" and scroll to the bottom of that list. These will persist until the Editor is restarted.

I first noticed this leak in Unity 2020.3.12f1 and confirmed it in 2020.3.14f1