new handles coming up after calling InitializeQTML ()

In article <EyBic.15913$N9.15003@news.chello.at>,
"Martin Nedbal" <martin DeleteThis @nedbal.net> wrote:

 > Hi guys,
 > I have little problem with QuickTime on windows, when I call InitializeQTML
 > (0) new handles start popping up - it is approximately two new handles per
 > second and it's still counting.
 >
 > I'm using current Qt SDK called from MSVC 6.0, QuickTime version 6.5 on
 > WindowsXP (patched with all hotfixes)
 >
 > This is simpliest sample code which causes described problem :
 >
 > #include <windows.h>
 > #include <QTML.h>
 > #include <Movies.h>
 > #include <Files.h>
 >
 > int APIENTRY WinMain(HINSTANCE hInstance,
 > HINSTANCE hPrevInstance,
 > LPSTR lpCmdLine,
 > int nCmdShow)
 > {
 > OSErr hr;
 >
 > hr = InitializeQTML(0);
 > hr = EnterMovies();
 >
 > while (true) Sleep (100);
 >
 > ExitMovies();
 > TerminateQTML();
 >
 > return 0;
 > }

You didn't call InitializeQTM() with the kQTMLNoIdleEvents flag, so
it wouldn't surprise me if you are seeing sludge build up because you
aren't properly calling Quicktime to handle its events. If you search
the header files for "Idle", you'll find a number of calls, not
including MoviesTask() that you should be calling.

This tech note might be helpful:
Tech Q&A QA1349 "How often should I call SGIdle()?"
<http://developer.apple.com/qa/qa2001/qa1349.html><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: new handles coming up after calling InitializeQTML () 

 >"David Phillip Oster" <oster.TakeThisOut@ieee.org> wrote in message
news:oster-311A2D.15452024042004@news.sf.sbcglobal.net...
 > In article <EyBic.15913$N9.15003@news.chello.at>,
 > "Martin Nedbal" <martin.TakeThisOut@nedbal.net> wrote:
 >
  > > Hi guys,
  > > I have little problem with QuickTime on windows, when I call
InitializeQTML
  > > (0) new handles start popping up - it is approximately two new handles
per
  > > second and it's still counting.
  > >
  > > I'm using current Qt SDK called from MSVC 6.0, QuickTime version 6.5 on
  > > WindowsXP (patched with all hotfixes)
  > >
  > > This is simpliest sample code which causes described problem :
  > >
  > > #include <windows.h>
  > > #include <QTML.h>
  > > #include <Movies.h>
  > > #include <Files.h>
  > >
  > > int APIENTRY WinMain(HINSTANCE hInstance,
  > > HINSTANCE hPrevInstance,
  > > LPSTR lpCmdLine,
  > > int nCmdShow)
  > > {
  > > OSErr hr;
  > >
  > > hr = InitializeQTML(0);
  > > hr = EnterMovies();
  > >
  > > while (true) Sleep (100);
  > >
  > > ExitMovies();
  > > TerminateQTML();
  > >
  > > return 0;
  > > }
 >
 > You didn't call InitializeQTM() with the kQTMLNoIdleEvents flag, so
 > it wouldn't surprise me if you are seeing sludge build up because you
 > aren't properly calling Quicktime to handle its events. If you search
 > the header files for "Idle", you'll find a number of calls, not
 > including MoviesTask() that you should be calling.
 >
 > This tech note might be helpful:
 > Tech Q&A QA1349 "How often should I call SGIdle()?"
 > <http://developer.apple.com/qa/qa2001/qa1349.html>

Hi David,
thanks for such a quick reply. Is this the correct flag definition ? Value
1L << 1 is shared by two flags (kInitializeQTMLUseGDIFlag and
kQTMLNoIdleEvents) ?

QTMH.h :

....
/* InitializeQTML flags*/
enum {
kInitializeQTMLNoSoundFlag = (1L << 0), /* flag for
requesting no sound when calling InitializeQTML*/
kInitializeQTMLUseGDIFlag = (1L << 1), /* flag for
requesting GDI when calling InitializeQTML*/
kInitializeQTMLDisableDirectSound = (1L << 2), /* disables
QTML's use of DirectSound*/
kInitializeQTMLUseExclusiveFullScreenModeFlag = (1L << 3), /* later
than QTML 3.0: qtml starts up in exclusive full screen mode*/
kInitializeQTMLDisableDDClippers = (1L << 4) /* flag for
requesting QTML not to use DirectDraw clipper objects; QTML 5.0 and later*/
};

enum {
kQTMLNoIdleEvents = (1L << 1) /* ask for a
non-auto-idled port to be created*/
};
....

Martin<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: new handles coming up after calling InitializeQTML () 

In article <aBDic.15985$N9.9229@news.chello.at>,
"Martin Nedbal" <martin.TakeThisOut@nedbal.net> wrote:

 > thanks for such a quick reply. Is this the correct flag definition ? Value
 > 1L << 1 is shared by two flags (kInitializeQTMLUseGDIFlag and
 > kQTMLNoIdleEvents) ?

<http://developer.apple.com/documentation/QuickTime/APIREF/SOURCESI/createportassociation.htm>

says that kQTMLNoIdleEvents gets passed to CreatePortAssociation.

Did you try the minimal sample Windows Quicktime program from:

<http://developer.apple.com/documentation/QuickTime/WIN/tp_qtwin_qtforwindows.5.htm>
Listing 2 (near the end of the page)?

int CALLBACK WinMain (HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR lpCmdLine, int nCmdShow){
MSG msg;
HANDLE hAccelTable;
OSStatus stat = noErr;

// Is there a previous instance? and couldn't Register window class? Report failure
if( ! hPrevInstance && ! InitApplication(hInstance)){
return FALSE;
}
if(noErr == stat){ stat = InitializeQTML(0); } // Initialize QTML
if(noErr == stat){ stat = EnterMovies(); } // Initialize QuickTime
if(noErr != stat){
MessageBox (hWnd, "QuickTime not available", "", MB_OK);
return FALSE; // Report failure
}
if( ! InitInstance(hInstance, nCmdShow)){ // Create main window
return FALSE; // Report failure
}
hAccelTable = LoadAccelerators(hInstance, MAKEINTRESOURCE(IDR_ACCELSIMPLESDI));


///////////////////////////////////////////////////////////////////////////////
// Main message loop
///////////////////////////////////////////////////////////////////////////////

while(GetMessage(&msg, NULL, 0, 0)){   // Retrieve next message
// Check for keyboard accelerator
if( ! TranslateAccelerator (msg.hwnd, hAccelTable, &msg)){
TranslateMessage(&msg);  // Convert virtual key to character
DispatchMessage(&msg);   // Send message to window procedure
}
}
///////////////////////////////////////////////////////////////////////////////
ExitMovies(); // Terminate QuickTime
TerminateQTML(); // Terminate QTML
return msg.wParam;

} /* end WinMain */<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: new handles coming up after calling InitializeQTML () 

 >"David Phillip Oster" <oster.DeleteThis@ieee.org> wrote in message
news:oster-55C6EC.22204424042004@news.sf.sbcglobal.net...
 > In article <aBDic.15985$N9.9229@news.chello.at>,
 > "Martin Nedbal" <martin.DeleteThis@nedbal.net> wrote:
 >
  > > thanks for such a quick reply. Is this the correct flag definition ?
Value
  > > 1L << 1 is shared by two flags (kInitializeQTMLUseGDIFlag and
  > > kQTMLNoIdleEvents) ?
 >
 >
<http://developer.apple.com/documentation/QuickTime/APIREF/SOURCESI/createpo
rtassociation.htm>
 >
 > says that kQTMLNoIdleEvents gets passed to CreatePortAssociation.
 >
 > Did you try the minimal sample Windows Quicktime program from:
 >
 >
<http://developer.apple.com/documentation/QuickTime/WIN/tp_qtwin_qtforwindow
s.5.htm>
 > Listing 2 (near the end of the page)?
 >
 > int CALLBACK WinMain (HINSTANCE hInstance, HINSTANCE hPrevInstance, LPSTR
lpCmdLine, int nCmdShow){
 > MSG msg;
 > HANDLE hAccelTable;
 > OSStatus stat = noErr;
 >
 > // Is there a previous instance? and couldn't Register window class?
Report failure
 > if( ! hPrevInstance && ! InitApplication(hInstance)){
 > return FALSE;
 > }
 > if(noErr == stat){ stat = InitializeQTML(0); } // Initialize QTML
 > if(noErr == stat){ stat = EnterMovies(); } // Initialize QuickTime
 > if(noErr != stat){
 > MessageBox (hWnd, "QuickTime not available", "", MB_OK);
 > return FALSE; // Report failure
 > }
 > if( ! InitInstance(hInstance, nCmdShow)){ // Create main window
 > return FALSE; // Report failure
 > }
 > hAccelTable = LoadAccelerators(hInstance,
MAKEINTRESOURCE(IDR_ACCELSIMPLESDI));
 >
 >
 >
////////////////////////////////////////////////////////////////////////////
///
 > // Main message loop
 >
////////////////////////////////////////////////////////////////////////////
///
 >
 > while(GetMessage(&msg, NULL, 0, 0)){ // Retrieve next message
 > // Check for keyboard accelerator
 > if( ! TranslateAccelerator (msg.hwnd, hAccelTable, &msg)){
 > TranslateMessage(&msg); // Convert virtual key to character
 > DispatchMessage(&msg); // Send message to window procedure
 > }
 > }
 >
////////////////////////////////////////////////////////////////////////////
///
 > ExitMovies(); // Terminate QuickTime
 > TerminateQTML(); // Terminate QTML
 > return msg.wParam;
 >
 > } /* end WinMain */

Jon, David,
thanks for your replies, it made me read the documentation properly at
least. However it seems to me that I've found (strange) bug - the handles
are from event objects, which seem to be stuck somewhere, there are system
treads (in blocked state) created for each event as well. I found out that
the sample application (mdiplayer.win) and even the QuickTime player (!)
behaves the same way BUT this behavior occurs AFAIK only when the process is
watched with ProcessExplorer (http://www.sysinternals.com/) in "DLL mode".
I'll tried to reproduce it on other versions of windows and I wasn't
successfull - it would be windows xp related. I'm going to gather as much
information as possible to report it to Apple.

Thanks for your time, I'll post the resolution from Apple here once I have
it.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: new handles coming up after calling InitializeQTML ()