[Helix-producer-issues] [Bug 15221] New: Memory leak with DirectShow

https://bugs.helixcommunity.org/show_bug.cgi?id=15221



guest created:

          Priority: P0                                                      
                CC: karll                                                   
  Operating System: other                                                   
        AssignedTo: apal                                                    
         QAContact: QA                                                      
           Summary: Memory leak with DirectShow                             
          Severity: S1                                                      
            Status: NEW                                                     
 Last changed date: 2006-05-08 22:39:03                                     
          Hardware: Other                                                   
           Version: unspecified                                             
           Tracker: ActiveX                                                 
           Project: helix-producer                                          
  Target Milestone: Gold                                                    

Hi

Producer leak big amount of memory that aren't freed after an encode completition. After 4 files,
SDK uses 150MB RAM and 512MB SWAP. I succeded to go to 2GB before my software crash.

I'm trying now to force the ActiveX to ReleaseRessources(); after each encode.

Talking about that bug with Karl, we discovered that it's a problem with DirectShow.

Softwares:
RealAnime 2.00RCx
AVISynth 2.5.5 (AVISource and DirectShowSource)
Lastest SDK (ActiveX)
------- Additional Comments From guest 2012-10-09 20:54 GMT-0800 -------
This bug is a clone of bug #2741, created by guest

-- 
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
You are in the CC list for the product the bug is within.


This e-mail is sent to you automatically from the Helix Bug Tracker.  Please, do
not respond to this message, but instead edit your Bug Tracker user preferences
to change when Bug Tracker sends you e-mail.