mciSendString cause thread handle leak on Win98 Me

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a problem when i use mciSendString on Win98 or WinMe
When I call mciSendString to open an avi file, it works but there is an additiona
thread handle ( I use sysinternal's process viewer to see this)
And after I call mciSendString again using "close" to close the file, the thread handle is stil
there....So this cause a handle leak..
I find a sample in msdn but it has the same problem
How to avoid this?
 
I have a problem when i use mciSendString on Win98 or WinMe.
When I call mciSendString to open an avi file, it works but there is an additional
thread handle ( I use sysinternal's process viewer to see this).
And after I call mciSendString again using "close" to close the file, the thread handle is still
there....So this cause a handle leak...
Click to expand...

If you call mciSendString again to open another file, do you get
another thread, or is it perhaps re-using the original one?

Dave
 
It just reuse the original thread. The number of thread does not increase
I think when I open another file, maybe it call OpenThread or sth that opens a handle
 
Back
Top