title: directshow H.264 encoder which never cause memory leak
body: <p>I'm developping H.264 capture application executed on Windows XP SP3(32bit).</p>
  
  <p>The application cause memory leak when I implement Capture Test<br/>
  (I'm checking Virtual Size colum of "Process Explorer").</p>
  
  <p>When I change directshow encoder filter, amount of leak is changed.
  So I'm suspecting directshow H.264 filter(encoder or multiplexor or both) as the cause of the memory leak.</p>
  
  <p>Would you please tell me if you have heard "Free" directshow H.264 filter which never cause memory leak?</p>
  
  <p>---- Follow up 2015-07-09 ----<br/>
  I execute the application on WindowsXP: leaked<br/>
  I execute the application on Windows 7 : not leaked</p>
  
  <p>Are there any difference related to memory allocation/free between XP and 7...?</p>
  
  <p>---- Follow up 2015-07-10 ----<br/>
  I checked constructed graph on WindowsXP and Windows7 using GraphStudioNext.<br/>
  H.264 Encoder : the same CLSID between WindowsXP and Windows7<br/>
  H.264 Multiplexor : the same CLSID between WindowsXP and Windows7<br/></p>
  
  <p>Now I have attempted the H.264 filters below.<br/></p>
  
  <ul>
  H.264 encoder: ffdshow_rev3572_20100913_clsid, AX_components H264 encoder, x264vfw<br/>
  H.264 multiplexor: GDCL-H.264Multiplexor(updated 05 Jun 2015)<br/>
  </ul>
  
  <p>On both platforms, graph is below.<br/>
  [USB Camera]---->[Smart Tee]---->[H.264 Encoder]---->[H.264 Mux]--->[File Writer]<br/></p>
  
  <p>matter of concern:</p>
  
  <ul>
  <li>In GraphStudioNext's Filter Propaties, WindowsXP using quartz.dll,<br/>
  but Windows7 using proppage.dll. Is this difference important..?<br/></li>
  <li>On Windows XP, ALLOCATOR PROPATIES are exists, but 7 are not exists.</li>
  </ul>