Re: Handle leak in DSOUND.DLL called from Quicktime 7 on Windows XP?

Begin forwarded message:

From: email@hidden
Date: May 19, 2006 4:19:54 PM PDT
To: email@hidden
Subject: Handle leak in DSOUND.DLL called from Quicktime 7 on Windows XP?

I've been trying to track down a resource leak in a product we've
developed, and to make life simpler, I'd created a similarly-functioned
test application that simply plays back a list of Quicktime files one
after another. It's in Delphi, and I ran a profiler on it to see where
resources were being used and lost.

What it looks like, based on my understanding of the output, is that
every time a Quicktime file is started, 6 handle get consumed by
DSOUND.DLL (possibly via DirectSoundCaptureEnumerateW) and never
released. It's consistent on several different machines here, but they
are all Windows XP Service Pack 2 with DirectX 9.0c and Quicktime 7 on
them.

This is not ringing any bells. We do not call DirectSoundCaptureEnumerate anywhere in the qt api. Your best bet would be to submit a bug report (bugreport.apple.com) and attach a sample project that we can build and run that displays the problem. Writing it in C/C++ would be a bonus.

Thanks.

-Brad Ford

QuickTime Engineering

Google, Google Groups, and searches on MSDN haven't revealed any
articles on known resource/handle leaks with DSOUND.DLL, but I'm not
sure I'm asking the right question to get relevant articles in the first
3 pages of search results.

Are there any known issues with DSOUND.DLL leaking resources? Or with
Quicktime's interaction with DirectSound?

Warrick Wilson