Elecard GraphViewer leaks memory cause fails to release PropPage objects

I have detected a problem using the GraphViewer COM object in an application where it fails to release objects if the same property page for an inserted filter is opened "more than once". The result is a memory leak and hold objects that may go bang sometime later !

One will clearly see this if one builds a debug filtergraph application and inserts the ELGView object and a simple filter that has a property page built using windows DirectShow SDK's CBasePropertyPage class. If you open the ElGView window and than open a PropertyPage for this filter once, than close the prop page, ELGView window and application - all goes well. But if you open the prop page on this same filter, than close it, and open it again, than close the ELGView window, than app re will see the Windows DirectShow SDK ObjectsActive() error message about unreleased objects left in memory.

I tracked this problem down to the ELGView object which apparently does not clean up properly if one reopens the same filter property page more than once - each time resulting in more objects not released. When we close the filter's property page, ELGView calls the prop page's Release() call subsequently SetPageSite(), OnDisconnect() then the Prop Page class destructor, but multiple re-opening of the same property page ELGView creates a new instance of the property page without cleaning up any previous same property pages.

I suggest the cleanest and easiest fix is to release the property page object "everytime the filter's property page is closed", not when the ELGView window is closed. If this is implemented, when could an update be available ?