Why sometimes Windows cannot kill a process?

Posted by Néstor Sánchez A. on Stack Overflow See other posts from Stack Overflow or by Néstor Sánchez A.
Published on 2010-03-20T01:18:25Z Indexed on 2010/03/20 1:21 UTC
Read the original article Hit count: 632

Filed under:
|
|

Right now I'm trying to Run/Debung my app on VisualStudio, but it cannot create it because the las instance of the app.vshost.exe is still running. Then, by using the Task Manager i'm trying to kill it, but it just remains there with no signal of activity.

Beyond that particular case (maybe a VS bug), i'm very curious about the technical reasons why sometimes Windows cannot kill a process???

Can, an enlighted OS related developer, please try to explain?

(And please don't start a Unix/Linux/Mac battle against Windows)

© Stack Overflow or respective owner

Why sometimes Windows cannot kill a process?

Posted by Néstor Sánchez A. on Super User See other posts from Super User or by Néstor Sánchez A.
Published on 2010-03-20T01:18:25Z Indexed on 2010/03/20 1:41 UTC
Read the original article Hit count: 632

Filed under:
|
|

Right now I'm trying to Run/Debung my app on VisualStudio, but it cannot create it because the las instance of the app.vshost.exe is still running. Then, by using the Task Manager i'm trying to kill it, but it just remains there with no signal of activity.

Beyond that particular case (maybe a VS bug), i'm very curious about the technical reasons why sometimes Windows cannot kill a process???

Can, an enlighted OS related developer, please try to explain?

(And please don't start a Unix/Linux/Mac battle against Windows)

© Super User or respective owner

Related posts about Windows

Related posts about process