So I'm guessing these processes are holding onto a communication endpoint, And in any case, if the parent is gone, surely the proper way to handle that is to let the child be killed without having to report, not to REFUSE to kill the child! because termination "has to be reported to the parent." I've seen that concept in other OSes, though I don't entirely agree with the idea from a design standpoint. My guess is that when I earlier killed off several chrome.exe processes (after Chrome became totally unresponsive), maybe one or more of those that I killed were the parents of these, and maybe those parents need to exist for the child to be properly terminated, e.g. Reason: there is no running instance of the task. Errors are of the formĮRROR: The process with PID 28264 (child process of PID 28448) could not be terminated. TASKKILL doesn't work, even when issued from a CMD session run as Administrator. Same problem on an old Win7 Laptop just now.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |