|
http://msdn2.microsoft.com/en-us/library/bb250462.aspx I think the best solution here is to use jobs, as described here http://benjamin.smedbergs.us/blog/2006-12-11/killableprocesspy/ The easiest thing might be to take the code in killableprocess (or something like it) and compile it into an exe that we can ship in the jar. The Best(tm) thing might be to use JNI, especially if we could figure out how to solve the problem of how to package DLLs in JARs and delete them when we're done. I discuss the idea of JNI in more detail in Fixed in rc revision 1984, which unfortunately also created Jean-Charles Meyrignac is reporting that this is still broken, so I did some more work to make it more reliable (by fixing I'm having issues with this on Vista. The manual test cases in killableprocess.cpp doesn't work. According to the last comment this issue is not completely fixed. As I don't have Vista could you please check Dan what's the problem? |
|||||||||||||||||||||||||||||||||||
Yup, watching via procexp, you can see clearly that we launch iexplore.exe, he spawns ieuser.exe, and then iexplore.exe dies; ieuser.exe then launches another iexplore.exe and that's the one you see on the screen.