I am trying to debug the memory leak of a UWP app. The memory profiling seems to suggest the leak is primarily on the native side: I cannot make any sense of the native memory data: Could anyone offer a tip on how to read these native memory data to find a clue about the leak? I think the leak is related to the use of MediaPlayerElement.

Hi Junjie, Thank you for all the help. I think I have at least found the culprit for the memory leak that I can reproduce on my testing PC. It is related to the handling of MeidStreamSource's events such as Closed, Paused, Starting. The app missed some subscriptions (e.g., it subscribed to 5 events but unsubscribed to only 3). I did not know this could cause so much memory leak despite all the objects being disposed of.

Native memory leak

Hong 1,141

I am trying to debug the memory leak of a UWP app. The memory profiling seems to suggest the leak is primarily on the native side:

User's image

I cannot make any sense of the native memory data:

Snag_3174f9b7 User's image

Could anyone offer a tip on how to read these native memory data to find a clue about the leak?

I think the leak is related to the use of MediaPlayerElement.

Junjie Zhu - MSFT 15,601 Reputation points Microsoft Vendor

2024-05-10T07:01:02.8233333+00:00

Hi @Hong ，

Welcome to Microsoft Q&A!

To further analyze this problem, I would appreciate your help to collect the following information.

1.How to use MediaPlayerElement to reproduce the behavior?

2.Does the memory continue to increase?

Thank you.
Hong 1,141 Reputation points

2024-05-10T09:43:57.9066667+00:00
Thank you for your trying to help, Junjie.

Great questions. I forgot to point out an important thing: the memory leak does not happen as long as the app keeps streaming from the same source. It happens only when the app exits the page. The memory footprint is like the following:

Start the app: 100MB

Start the video streaming: 120MB

Exit the streaming page: 120MB

Start the video streaming again: 140MB

Exit the streaming page again: 140MB

Start the video streaming again: 160MB

Exit the streaming page again: 160MB

...

The above numbers are not exact actual numbers, but just indicative.

The app uses MediaPlayerElement like the following:

mpeVideo = new MediaPlayerElement();

mpeVideo.Source = MediaSource.CreateFromMediaStreamSource(myMediaStreamSourceVideo)

mpeVideo.MediaPlayer.RealTimePlayback = true;

mpeVideo.MediaPlayer.Play();

...

mpeVideo.MediaPlayer.Pause();

mpeVideo.MediaPlayer.Dispose();

Most of the work is done in myMediaStreamSourceVideo. The code is quite large (thousands of lines). I just extracted the relevant parts here to give an idea.
Junjie Zhu - MSFT 15,601 Reputation points Microsoft Vendor

2024-05-15T03:54:19.52+00:00

Hi @Hong ，

Start the video streaming again: Exit the streaming page:

Are you using Frame.Navigate to exit pages? It seems that popup is the better option.
Junjie Zhu - MSFT 15,601 Reputation points Microsoft Vendor

2024-05-16T07:57:39.01+00:00

Hi @Hong ，

Glad to hear that. If your problem is solved, you can share your solution with answer.
Hong 1,141 Reputation points

2024-05-16T13:18:08.6633333+00:00

Hi Junjie, I converted my comment to an answer per your suggestion.

1 answer

Hong 1,141 Reputation points

2024-05-16T03:28:42.87+00:00

Hi Junjie,

Thank you for all the help.

I think I have at least found the culprit for the memory leak that I can reproduce on my testing PC. It is related to the handling of MeidStreamSource's events such as Closed, Paused, Starting. The app missed some subscriptions (e.g., it subscribed to 5 events but unsubscribed to only 3). I did not know this could cause so much memory leak despite all the objects being disposed of.
Please sign in to rate this answer.

1 person found this answer helpful.

0 comments No comments
Sign in to comment

Share via

Native memory leak

1 answer