> The real problem is that your program never closes the thread handles;
> this causes a descriptor leak because we wait until the last close to
> release the thread buffer.
Oops!! I can't believe I missed that! I pulled the threading
code out of the app I was testing, simplified as much as I could
done to the state I posted to the mailing list, and all along
I missed the fact the thread handle wasn't being closed.
The easiest fixes are the ones most easily missed, I guess.
I guess this problem shows itself faster in WINE due to
the client/server socket communication mechanism.
Also, wine's behaviour is correct, the thread buffer has to
be kept around until the last handle is closed, according to
MSDN.
Unfortunately, even when closing the thread handles
properly the test app crashes on the Corel Wine tree, so on
our tree there is some other underlying problem
(that has been fixed over the past few months in
WineHQ's tree)
> Following patch should fix this and allow
> your test app to exhaust available memory instead ;-)
I think I should fix my app instead, since Wine is
following windows behaviour. ^_^
Thanks a lot for your help,
-James
--
James Hatheway
Software Developer - Macadamian Technologies, Inc.
[EMAIL PROTECTED] ~ http://www.macadamian.com
"Nothing is a problem once you debug the code."
John Carmack
