Re: DirectShow heap memory leak
From: Michael Schwab (michael.schwab_at_cobecv.com)
Date: 01/08/05
- Next message: Joe Flynn: "Re: DirectShow heap memory leak"
- Previous message: Thore Karlsen [MVP DX]: "Re: DirectShow heap memory leak"
- In reply to: Thore Karlsen [MVP DX]: "Re: DirectShow heap memory leak"
- Next in thread: Thore Karlsen [MVP DX]: "Re: DirectShow heap memory leak"
- Reply: Thore Karlsen [MVP DX]: "Re: DirectShow heap memory leak"
- Messages sorted by: [ date ] [ thread ]
Date: Fri, 7 Jan 2005 17:41:05 -0700
Yes, that's what I'm saying.
And I know something is seriously wrong!
How do I fix it?
"Thore Karlsen [MVP DX]" <sid@6581.com> wrote in message
news:5j2ut0lm4vfg7bd62hci7fho33kqso19qj@4ax.com...
> On Fri, 7 Jan 2005 14:56:44 -0700, "Michael Schwab"
> <michael.schwab@cobecv.com> wrote:
>
> >Working backwards is a great idea - here goes:
> >
> >- Already had the pVidWin stuff commented out.
> >- Commented out the Run() and the infinite wait - still have the memory
> >leak.
> >- Commented out the Stop() and the RenderFile() - still have the memory
> >leak.
> >- Commented out the QueryInterface() for pControl and pEvent, and also
their
> >Release calls - still have the memory leak.
> >- Commented out the CoCreateInstance() and pGraph->Release() calls - no
more
> >memory leak! (Not surprising because the CoInitialize wasn't using any
heap
> >space anyway, and that's all that was left).
> >- Uncommented the CoCreateInstance() call but left the pGraph->Release()
> >call commented out - now the memory doubles to 2.097 Mb, which is the
amount
> >that the CoCreateInstance() call usually takes.
> >
> >So for some reason the pGraph->Release() is only freeing up exactly half
the
> >space that CoCreateInstance() has allocated. And calling
pGraph->Release()
> >doesn't help, and sometimes crashes it (especially under WinXP).
> >
> >So what's wrong with my CoCreateInstance() call? Is it that pGraph is a
> >local (stack?) variable?
>
> Let me see if I understand correctly. This example would produce a
> memory leak:
>
> CoInitialize();
> CoCreateInstance(... &pGraph);
> pGraph->Release();
> CoUninitialize();
>
> Is that what you are saying? This leaks when absolutely no other code is
> executed? If that's the case, there's something seriously wrong with
> your system. :)
>
> --
> New to newsgroups? Read: http://dev.6581.com/newsgroups.html
- Next message: Joe Flynn: "Re: DirectShow heap memory leak"
- Previous message: Thore Karlsen [MVP DX]: "Re: DirectShow heap memory leak"
- In reply to: Thore Karlsen [MVP DX]: "Re: DirectShow heap memory leak"
- Next in thread: Thore Karlsen [MVP DX]: "Re: DirectShow heap memory leak"
- Reply: Thore Karlsen [MVP DX]: "Re: DirectShow heap memory leak"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
