now watches the IPC thread owner and will cancel the active IPC search if the thread is terminated
Is this actually happening?
At least there continues CPU, disk I/O activity after the "Quit" (Ctrl+C).
(How long that continues, can be variable, sometimes very long, sometimes relatively short, but activity seems to be there.)
now watches the IPC thread owner and will cancel the active IPC search if the thread is terminated
Is this actually happening?
At least there continues CPU, disk I/O activity after the "Quit" (Ctrl+C).
(How long that continues, can be variable, sometimes very long, sometimes relatively short, but activity seems to be there.)
That's what I'm seeing, too:
ES.exe talks to Everything and asks it to produce some results.
If this thread is termnated (Ctrl-C), then ES.exe "hangs up" without telling Everything.exe that the results are no longer needed.
So Everything.exe keeps busy, untl it is ready to pass the results to ES.exe and finds out the line is dead.