I just wanted to ask you if you perhaps found any solution or any info about the crash you mentioned in your post about the Haali Media Splitter.I have the same crash. Looking at the mailinglist for the Haali Media Splitter, a Microsoft employee also posted about the same crash, but no response at all from the developers.

I’m looking to use the splitter in a commercial application so it’s quite saddening to see no response from Mike (I think that’s his name)
http://lists.matroska.org/pipermail/matroska-devel/2009-October/003557.html
I never thought Microsoft would actually look at those dumps if the code responsible wasn’t theirs.

Well, I don’t already remember the details, but I think that even if the problem is here, you can in your application just use try/catch block to catch the exception. I am not sure if this can really work, but this is the first thing to try.

If this is does not work, you can leave the graph and the filter not released. This will create a memory leak, of course, but you can remove other filters which you can remove safely so that the effect is minimal. Once the problem is fixed you will return to normal release/destruction.

Both ways are of a kind that you normally avoid, but it is going to work in most cases as a workaround.