Re: Win32 TerminateProcess problem

For what it is worth, TerminateProcess is a terrible thing to call. It is
documented to leak resources, and it will have a real impact on your system
performance, all from making it slowly slower to just making it unusable in
a couple of minutes. The "best" way I'm aware of is to start a remote thread
in the process you want to kill and call exit from that thread (which will
allow the process cleanup to run).



On Wed, Feb 3, 2010 at 5:28 PM, Emil Dotchevski <[email protected]>wrote:

> On Wed, Feb 3, 2010 at 5:17 PM, Jon Watte <[email protected]> wrote:
> > You want to get consistent results from an IPC signal, without
> > synchronization, on a pre-emptively scheduled machine?
> > It's good to want things and all, but I don't see how that problem, in
> > general, could ever be made to work 100% reliably.
>
> It works 100% reliably on Windows 7. Also, I haven't found anything in
> the documentation that hints that my code shouldn't work as expected.
> What am I missing?
>
> Emil Dotchevski
> Reverge Studios, Inc.
> http://www.revergestudios.com/reblog/index.php?n=ReCode
> _______________________________________________
> Sweng-Gamedev mailing list
> [email protected]
> http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com
>



-- 
Introspection is just a ladder for people who have dug them an object
oriented hole.

_______________________________________________
Sweng-Gamedev mailing list
[email protected]
http://lists.midnightryder.com/listinfo.cgi/sweng-gamedev-midnightryder.com