You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in Jupyter notebook, and press "Interrupt the kernel" for the first time, I get some output but the workers are still working. After hitting "Interrupt the kernel" for the second time, most workers are killed (44 on my machine), but (always) 4 are still working 100% CPU. Only hitting "Interrupt" for the third time, clears everything.
Here is my workaround with which "Interrput" works with the first hit
Thanks for the bug report. I am using pool.join() instead of terminate, I don't know why that makes the difference, but it makes sense that terminate does not wait for anything to finish.
I will try to find time to fix this. I would like to use pool.join unless there is an error or an interruption.
If I run something like that
in Jupyter notebook, and press "Interrupt the kernel" for the first time, I get some output but the workers are still working. After hitting "Interrupt the kernel" for the second time, most workers are killed (44 on my machine), but (always) 4 are still working 100% CPU. Only hitting "Interrupt" for the third time, clears everything.
Here is my workaround with which "Interrput" works with the first hit
The text was updated successfully, but these errors were encountered: