This is a weird one. When I KeyboardInterrupt in a Jupyter Notebook, a very CPU hungry Python process starts.

When I restart the kernel, it terminates. If I terminate it in the activity monitor, the Jupyter kernel becomes busy (no output in terminal).
Even weirder, if I launch a new visualization, IT STOPS.
This is a weird one. When I
KeyboardInterruptin a Jupyter Notebook, a very CPU hungry Python process starts.When I restart the kernel, it terminates. If I terminate it in the activity monitor, the Jupyter kernel becomes busy (no output in terminal).
Even weirder, if I launch a new visualization, IT STOPS.