Repository navigation
Closed
Labels
info-neededIssue requires more information from posterIssue requires more information from poster
Description
Type: Bug
Behaviour
Send line to terminal fails to send after some time of working. This is easiest to trigger when waking from a sleep, but also happens if the terminal was killed.
Restarting VSCode & Python Extensions doesn't fix it. I've also tried turning on / off Python extension but this doesn't always seem to fix it either.
The sendline is only broken for that project. Opening another different project where the hang/bug has happened and send line will work correctly.
Full computer restart always fixes it.
Steps to reproduce:
- Innactivity seems to be the most consistent way this happens, I believe sleep.
Diagnostic data
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
XXX
Extension version: 2026.5.2026070801
VS Code version: Code 1.129.1 (8a7abeba6e03ea3af87bfbce9a1b7e48fed567b8, 2026-07-17T15:35:09Z)
OS version: Linux x64 7.0.0-27-generic
Modes:
- Python version (& distribution if applicable, e.g. Anaconda): 3.12.13.final.0
- Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): System
- Value of the
python.languageServersetting: Default
User Settings
languageServer: "Pylance"
Installed Extensions
| Extension Name | Extension Id | Version |
|---|---|---|
| black-formatter | ms- | 2026.6.0 |
| copilot-chat | Git | 0.57.0 |
| debugpy | ms- | 2026.6.0 |
| even-better-toml | tam | 0.21.2 |
| github-vscode-theme | Git | 6.3.5 |
| js-debug | ms- | 1.117.0 |
| js-debug-companion | ms- | 1.1.3 |
| jsts-chat-features | Typ | 0.0.4 |
| python | ms- | 2026.5.2026070801 |
| svelte-vscode | sve | 110.3.0 |
| vim | vsc | 1.32.4 |
| vscode-js-profile-table | ms- | 1.0.10 |
| vscode-pylance | ms- | 2026.2.1 |
| vscode-python-envs | ms- | 1.36.0 |
System Info
| Item | Value |
|---|---|
| CPUs | 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 4150) |
| GPU Status | 2d_canvas: enabled GPU0: VENDOR= 0x10de, DEVICE=0x25a0, DRIVER_VENDOR=Mesa, DRIVER_VERSION=26.0.3 GPU1: VENDOR= 0x8086, DEVICE=0x9a60, DRIVER_VENDOR=Mesa, DRIVER_VERSION=26.0.3 ACTIVE Machine model name: Machine model version: direct_rendering_display_compositor: disabled_off_ok gpu_compositing: enabled multiple_raster_threads: enabled_on opengl: enabled_on rasterization: enabled raw_draw: disabled_off_ok skia_graphite: disabled_off trees_in_viz: disabled_off video_decode: enabled video_encode: disabled_software vulkan: disabled_off webgl: enabled webgpu: enabled webgpu_on_vk_via_gl_interop: enabled webnn: disabled_off |
| Load (avg) | 1, 1, 1 |
| Memory (System) | 61.27GB (49.42GB free) |
| Process Argv | --crash-reporter-id 0f47ba33-9d7e-4297-8478-a40a8b196674 |
| Screen Reader | no |
| VM | 0% |
| DESKTOP_SESSION | ubuntu |
| XDG_CURRENT_DESKTOP | ubuntu:GNOME |
| XDG_SESSION_DESKTOP | ubuntu |
| XDG_SESSION_TYPE | wayland |
A/B Experiments
vsliv368:30146709
binariesv615:30325510
nativeloc1:31344060
dwcopilot:31170013
dwoutputs:31242946
copilot_t_ci:31333650
e5gg6876:31282496
pythonrdcb7:31342333
6518g693:31463988
aj953862:31281341
63221493:31336333
envsactivate1:31551504
cloudbuttont:31379625
3efgi100_wstrepl:31403338
55ia6109:31457054
ddidt:31399633
ec5jj548:31422691
cp_cls_t_966_ss:31526232
4je02754:31466945
8hhj4413:31478653
38bie571_auto:31426784
cp_cls_c_1081:31454833
conptydll_true:31498968
e9c30283:31461165
test_treatment2:31471001
c9b86496:31447327
capico_a_098a3278:31551523
idci7584:31464702
e3e4d672:31494082
ei9d7968:31496641
chat:31457767
8hig5102:31480529
89g7j272:31518289
7e187181:31503455
i2gc6536:31499202
52612955:31516516
ghj88844:31499326
23c7c724:31520045
ddid_t:31478206
hmra_i5g22:31518061
ie3bb177:31543534
7df3h592:31512476
cp_cls_t_1082:31535311
logging_enabled_new:31498466
j0d79568:31499440
jb_cp_cls_t_632:31543129
852d2892:31506239
56dj4588:31512888
32d76977:31512328
ha629193:31508444
cdk-lw-on:31524445
f9bf7985:31543584
jh5f2457_c:31540921
41836166:31537719
jbcp_cls_pctr_t:31531130
61138546:31518536
cp_intellij_t_nes:31548657
jf4hg949:31526829
nes-curr-leftover-1500:31538366
ahp-both-windows:31552051
h561g132:31533256
sessions_5:31532894
ihg5j128:31534457
f412h606:31551416
7g2b5551:31542111
sandbox-ui-on-2:31543161
nes-ex-cf-euporie-03:31542868
allow-none:31552288
6i51c363:31551401
Metadata
Metadata
Assignees
Labels
info-neededIssue requires more information from posterIssue requires more information from poster
Activity
eleanorjboyd commentedon Sep 23, 2026
🤖 Thanks for the report. The current code resets its cached terminal and REPL state when VS Code reports that a terminal closed, so we need a little more information to identify what remains stale here. Please confirm this on the latest Python extension and provide exact steps plus trace-level output from the Python, Terminal, and Pty Host output channels after the failure; also let us know whether the terminal remains visible, whether its shell process has exited, and whether manually closing that terminal causes the next Shift+Enter to create a working one. Issues marked
info-neededautomatically close after 30 days without a reply.github-actions commentedon Oct 24, 2026
Hey Anthony Kim (@anthonykim1), this issue might need further attention.
James O'Claire (@ddxv), you can help us out by closing this issue if the problem no longer exists, or adding more information.
ddxv commentedon Nov 11, 2026
Hello, this problem is still happening on computer sleeps / after long periods of time with the latest versions of vscode-python and vscode.
When it triggers any amount of closing / opening new shells does not fix the issue. The shells look fine, pressing Send Line (Ctrl Enter) will open a new interpreter if one does not exist yet, and that interpreter works fine, just the lines seem to never be sent. I also can sometimes get it to work by switching several times the vscode python extension from Stable -> Pre-Release and back.
But what you said made me realize I should actually be clearing the cache. This time I tried "Python: Clear Cache and Reload Window" and this immediately fixed my issue!
I don't have the traces from when this happens, and given that it seems very unique to me (no other people have joined this issue), I will close the issue for now.