Quit Jupyter notebook without shutting down Slicer kernal - Slicer instance is persisting


I was running a Jupyter notebook script connected to a Slicer kernel. I accidentally quite the instance of Jupyter notebook (closed out of the window in browser) without first shutting down the Slicer kernel. Now I have an instance of Slicer that still says “Application is managed by Jupyter” and if closed it reopens itself.

Restarting the computer did not resolve the issue (this has worked in the past but isn’t in this current case). Reopening Jupyter in the browser did not help, as it doesn’t recognize any kernels as being open/running.

Does anyone know of a way to kill the Slicer instance that is being managed by Jupyter if Jupyter doesn’t seem to recognize the connection?

Thank you in advance for any assistance!

This is a very common complaint for Jupyter.

Restarting the computer should resolve this because Jupyter server is shut down when you restart your computer and the server is not started automatically when you log in. Hibernating or putting your computer to sleep will not help, as it does not shut down applications.

You can get the URL of running jupyter servers (so that you can open them in your web browser and shut down) as described here.

Alternatively, you can open Windows Task manager, go to “Details” tab, right-click on each python-real.exe process and choose “End task”.

1 Like

Thank you Andras!

The problem does appear to have resolved after a couple more restarts - not sure why the first attempts with that did not work; it sounds like they should have based on the way the Jupyter server is set up.

Thank you also for the information about getting the URL of the running Jupyter servers and the approach of using Windows Task Manager as an alternative approach. Greatly appreciate your helpful advice on this issue!

1 Like