Repository navigation
Notebook unresponsive after server is removed. #200
Description
Description
There are a variety of ways in which servers are removed. They can be explicitly removed through the Colab: Remove Server command, pruned due to inactivity or pruned once the server's lifetime is exceeded. In all cases, there's a bug where open notebook editors which were previously attached become unresponsive. The underlying issue is in the Jupyter extension and is reported in microsoft/vscode-jupyter#17094.
Environment
- VS Code version: All
- Colab extension version:
0.0.1 - Jupyter extension version:
2025.9.1 - OS (Linux | Mac | Windows): All
Repro Steps
- Create a Colab server.
- Run a cell.
Colab: Remove Server.- Try and run the cell on a new server (Colab or otherwise).
Expected Behaviour
The cell can be ran.
Actual Behaviour
The cell can't be ran. The notebook editor is unresponsive until reloaded (e.g. close and re-open the file).
Additional context
Logs
Logs from Colab in the Output panel (View > Output, change the drop-down the upper-right of the Output panel to Colab).
[2025-11-10T21:34:02.994Z] [Info] Visual Studio Code: 1.105.1
[2025-11-10T21:34:02.994Z] [Info] Remote: ssh-remote
[2025-11-10T21:34:02.994Z] [Info] App Host: desktop
[2025-11-10T21:34:02.994Z] [Info] Jupyter extension version: 2025.9.1Logs from Jupyter in the Output panel (View > Output, change the drop-down the upper-right of the Output panel to Jupyter).
All logs: jupyter-logs.txt
Key issue:
21:34:35.423 [error] Error in notebook cell execution Error: notebook controller is DISPOSED
Activity
aribornstein commentedon Nov 14, 2025
I ran into this issue as well had to restart vscode to use the notebook with another kernel.
amtoney524 commentedon Nov 14, 2025
hi @aribornstein - before restarting VS Code, did you try closing and reopening the notebook? Reloading the notebook should be enough to connect it to another kernel, but please let us know if that's not working for you!
kevineger commentedon Dec 23, 2025
microsoft/vscode-jupyter#17094 was recently merged! I'll keep an eye on releases and close our tracking issue once the fix is live.