How to free WMP object in WPF

Question

1.00/5 (1 vote)

See more:

I have implemented WMP in my WPF app. It plays .mp4 file for me. My target system is Win XP with low configuration. I play .mp4 videos repeatedly on app. It works as I expected but after some time it stops working and black screen appears. I know its the problem of freeing WMP object from memory. Here in my case WMP object goes out of CLR scope that's why CLR is not able to free its object and memory dumps. Can you guys please give me some suggestion to release this object from memory so my app doesn't stop and works well. Thank you.

C#

public void ReleaseWindowsMediaControl(AxWMPLib.AxWindowsMediaPlayer player)
{
try
{
if (player != null &amp;&amp; !player.IsDisposed)
{
player.MediaError -= new AxWMPLib._WMPOCXEvents_MediaErrorEventHandler(_windowMediaPlayer_MediaError);
player.PlayStateChange -= new AxWMPLib._WMPOCXEvents_PlayStateChangeEventHandler(_windowMediaPlayer_PlayStateChange);
if (player.currentMedia != null)
{
player.Ctlcontrols.stop();
player.currentPlaylist.clear();
}
player.close();
if (!System.Environment.OSVersion.ToString().ToUpper().Contains(&quot;NT 5.1.2600&quot;))
{
using (player)
{

}
player = null;
}
if (player != null)
{
player.Dispose();
} }
}
catch (Exception genericException)
{

}
}

I am using this code to release WMP object, but still I am facing the same issues.
See, I have 4 mp4 videos playing repeatedly one after another. First time all four videos played fine after finishing forth video player freezed, it'll not play first video after forth one. I know its memory leak problem but not able to solve this. so please help.

Posted 10-May-15 20:49pm

kailash_tandel87

Updated 11-May-15 19:22pm

v2

Add a Solution

Comments

Sergey Alexandrovich Kryukov 11-May-15 3:08am

Not enough information.
—SA

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2015-05-10T21:13:00

First of all, make sure you know which of the classes you use implement System.IDisposable and call System.IDisposable.Dispose on all instances. Also, there are types which implement some Dispose methods not related to this interface; check it up.

Also, make sure you understand stuff related to possible memory/resource leaks I explain in my past answers:
Memory leak in WPF DataBinding[^],
Memory management in MDI forms[^],
Best way to get rid of a public static List Causing an Out of Memory[^],
deferring varirable inside the loop can cuase memory leak?[^],
Garbage collectotion takes care of all the memory management[^].

[EDIT]

Let's see. This is a copy from your code in comment:

C#

//...
    player = null;
}
if (player != null)
{
    player.Dispose();
}

This is an apparent possibility of a leak. Do I even have to explain why? You should not assign an object to null.

And this is is just wrong

C#

using (player) {/* ... */}

And this is just crime (against yourself?):

C#

try {
   // ...
}
catch (Exception genericException)
{

}

You are completely blocking propagation of exception, and even without any handling. You should not do exception handling at this point at all, let it propagate. Learn how exceptions work.

—SA