AVIFileGetFrame memory leak
- From: "E. Nordhagen" <enordhag@xxxxxxxxxxxxx>
- Date: Thu, 19 May 2005 11:13:00 +0200
I have a server that generates AVI files (as a step to creating H263) on
demand. I use the AVI Stream functions provided with Visual Studio in C++.
It
leaks 16 bytes of memory each time an AVI video is created according to
Purify. I have run various versions of the code (the VS 6.0 example, our
full
applications, simplified versions...), and they all leak the same amount of
memory. I've checked initialization, release stuff etc. etc. with no luck in
removeing the leak.
I've tried reading both wav and avi files as input, and get the same leak.
The simplest version of this program is found at:
http://www.facems.com/else/SimpleLeak.html
I've also tested VS .Net 2003 with the same results. The examples here also
leak memory.
Report from purify runs at: http://www.facems.com/else/PurifyReport.txt
I really need to get rid of the memory leak to get a stable server, so all
help is greatly appreciated.
More details:
The audio format I use is uncompressed wav as input (PCM). I have followed
the
example aviview in doing the following:
Open the wav-file as an AVI file using AVIFileOpen, then create an avi
stream from this file using AVIFileGetStream.
Next, initialize an AVISTREAMINFO. Here it reads data from the above
mentioned input avi stream and fills in the AVISTREAMINFO. This is done in
function InitStreams() that you find on the specified html file from my
first
post.
This is similar to how the AVISTREAMINFO is set for the animation part (not
included in the above html file), and, as mentioned, the animation part does
not leak memory (and is not compressed either).
Then AVISaveV is called with the AVISTREAMINFO as parameter, followed by
AVISaveOptionsFree and AVIStreamClose and AVIFileClose.
There is no memory leak when following the same steps, but only creating
animation.
.
- Follow-Ups:
- RE: AVIFileGetFrame memory leak
- From: Rhett Gong [MSFT]
- RE: AVIFileGetFrame memory leak
- From: Rhett Gong [MSFT]
- RE: AVIFileGetFrame memory leak
- Prev by Date: Joining 2 audio channels
- Next by Date: Re: Access AVI in resource dll with AVI API
- Previous by thread: Joining 2 audio channels
- Next by thread: RE: AVIFileGetFrame memory leak
- Index(es):
Relevant Pages
|
