TerminateProcess and deadlocks?

Yes, all kernel objects held by the process will be released, including locks.

Yes, all kernel objects held by the process will be released, including locks. The main problem with TerminateProcess is that the process has no say in the matter: if it's holding on to any global state (files, shared memory, etc) then you have no guarantee those things are in a consistent state after the process is terminated.

– Tony The Lion May 25 '10 at 21:24 If it has pending I/O, the kernel waits for pending I/O to complete before terminating the process. If the process is in kernel-mode then it will also wait until that has finished (both of those are quite rare and will usually indicate a bad driver or bad hardware) – Dean Harding May 25 '10 at 21:33.

Yes. So long as you have the right permissions, TerminateProcess will kill the other process dead, regardless of how well hung it is.

TerminateProcess will kill each thread (as if TerminateThread had been used on each and every thread in the process). But it won't kill threads that are stuck in the kernel (e.g. Due to device driver bug).

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.