search

vyppN / aforge

Automatically exported from code.google.com/p/aforge
Other
0 stars 0 forks source link

Memory Leak in AForge.Video.FFMPEG.VideoFileWriter's Open Close Method. #319

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.Create VideoFileWriter instance
2.Open video file
3.Close video file
4.Dispose the instance
Do this in for loop to create 100 instances.

What is the expected output? What do you see instead?
Memory should not increase. It should release memory as its disposed.

What version of the product are you using?
2.2.4

Please provide any additional information below.
This leads to memory leak in application.

Original issue reported on code.google.com by wajeedsh...@gmail.com on 10 Oct 2012 at 11:36

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
Maybe. So what now?

Original comment by andrew.k...@gmail.com on 14 Oct 2012 at 6:11

GoogleCodeExporter commented 8 years ago 
Maybe you face the problem and try to solve it!

We have made the same experience with version 2.2.4. Unmanaged memory is 
growing steadily when you create a VideoFileWriter, open it, close it and 
dispose it afterwards.

Original comment by manuel.h...@dataformers.at on 12 Apr 2013 at 7:25

GoogleCodeExporter commented 8 years ago 
>> Maybe you face the problem and try to solve it!
What are you trying to say with this? Like to give a push - do it finally?

Original comment by andrew.k...@gmail.com on 12 Apr 2013 at 8:02

GoogleCodeExporter commented 8 years ago 
Exactly ;-)

Because your first response didn't sound as you would try to handle the problem.

If I can help you, please let me know how.

Greetings, Manuel

Original comment by manuel.h...@dataformers.at on 12 Apr 2013 at 8:12

GoogleCodeExporter commented 8 years ago 
OK, I may need to remind you one thing ... I am not obliged to anyone to do 
anything. If I have time - I do it. If not, then not. The project is open, so 
you are welcome to go through the code. So the way you push will not help in 
any way.

>> If I can help you, please let me know how.
Yes, you can. Fix the problem and send the patch to the benefit of others.

Original comment by andrew.k...@gmail.com on 12 Apr 2013 at 8:17

GoogleCodeExporter commented 8 years ago 
I'm looking into this, as it's blocking some efforts with HD video. If anyone 
has any hints I'm more than happy to receive them, otherwise I will post any 
updates if/when they come.

Original comment by cakest...@gmail.com on 27 Apr 2013 at 5:24

GoogleCodeExporter commented 8 years ago 
Has anyone found a fix for this?

Original comment by alexleykin on 17 Oct 2013 at 4:41

GoogleCodeExporter commented 8 years ago 
Pretty sure the bug is in ffmpeg itself as the memory leak only occurs on 
certain streams (mainly RTSP streams)

Original comment by ad...@developerinabox.com on 18 Oct 2013 at 1:24

GoogleCodeExporter commented 8 years ago 
Fixed. See issue #406.

Using avformat_free_context() instead of av_free() to properly free FFmpeg's 
format context.

Original comment by andrew.k...@gmail.com on 5 Jun 2015 at 11:24