Window Not Responding Error

[ly510]

Type: Performance Issue

It happened around 1pm today after code execution. Occur when I open one of my jupyter notebook.

VS Code version: Code - Insiders 1.101.0-insider (0264176, 2025-06-05T21:03:39.096Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item	Value
CPUs	12th Gen Intel(R) Core(TM) i5-12500 (12 x 2995)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: enabled_on 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 video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled webnn: disabled_off
Load (avg)	undefined
Memory (System)	15.70GB (2.66GB free)
Process Argv	--crash-reporter-id 1b712dfc-24ad-4f8e-97d9-385324d7fc7e
Screen Reader	no
VM	0%

Process Info

CPU %	Mem MB	   PID	Process
    1	   165	 17780	code-insiders
    1	   290	  6660	   gpu-process
    0	   135	 13492	pty-host
    0	     9	 24172	     "c:\Users\TayLiYin\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\node_modules\node-pty\build\Release\conpty\OpenConsole.exe" --headless --width 80 --height 30 --signal 0x4d4 --server 0x4cc
    0	    95	 31984	     C:\Users\TayLiYin\AppData\Local\Microsoft\WindowsApps\Microsoft.PowerShell_8wekyb3d8bbwe\pwsh.exe -noexit -command "try { . \"c:\Users\TayLiYin\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\out\vs\workbench\contrib\terminal\common\scripts\shellIntegration.ps1\" } catch {}"
    8	   156	 15404	   window
    0	    29	 21624	   crashpad-handler
    2	   295	 22776	window [1] (Process Explorer - 90 DATA ADHOC - Visual Studio Code - Insiders)
    0	    46	 27568	   utility-network-service
    0	   118	 28440	file-watcher [1]
    0	   612	 29032	extension-host [1]
    0	   118	  1560	     electron-nodejs (server.js )
    0	    68	  1628	     c:\Users\TayLiYin\anaconda3\envs\predict\python.exe -m ipykernel_launcher --f=c:\Users\TayLiYin\AppData\Roaming\jupyter\runtime\kernel-v37b5c39e1eca191a66c2614e3620a5bd1389d0ba5.json
    0	    11	  3776	       C:\Windows\system32\conhost.exe 0x4
    0	    95	  6380	     "C:\Users\TayLiYin\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe" "c:\Users\TayLiYin\AppData\Local\Programs\Microsoft VS Code Insiders\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=29032
    0	     8	 13696	     c:\Users\TayLiYin\.vscode-insiders\extensions\ms-python.python-2025.7.2025060501-win32-x64\python-env-tools\bin\pet.exe server
    0	    11	 17944	       C:\Windows\system32\conhost.exe 0x4
    0	  1096	 14148	     electron-nodejs (bundle.js )
    0	    17	 22880	     c:\Users\TayLiYin\anaconda3\envs\predict\python.exe c:\Users\TayLiYin\.vscode-insiders\extensions\ms-toolsai.jupyter-2025.5.2025060601-win32-x64\pythonFiles\vscode_datascience_helpers\kernel_interrupt_daemon.py --ppid 29032
    0	    11	 18456	       C:\Windows\system32\conhost.exe 0x4
    0	   190	 30560	shared-process

Workspace Info

|  Window (Process Explorer - 90 DATA ADHOC - Visual Studio Code - Insiders)
|    Folder (90 DATA ADHOC): 535 files
|      File types: txt(71) xlsx(70) json(69) csv(58) html(42) pdf(28) xls(28)
|                  png(20) ipynb(14) jpeg(10)
|      Conf files: settings.json(1);

Extensions (23)

Extension	Author (truncated)	Version
vscode-django	bat	1.15.0
python-environment-manager	don	1.2.7
python-extension-pack	don	1.7.0
copilot	Git	1.330.0
copilot-chat	Git	0.28.2025060502
vscode-test-explorer	hbe	2.22.1
vsc-python-indent	Kev	1.21.0
vscode-python-test-adapter	lit	0.8.2
debugpy	ms-	2025.9.2025053001
python	ms-	2025.7.2025060501
vscode-pylance	ms-	2025.5.101
jupyter	ms-	2025.5.2025060601
jupyter-keymap	ms-	1.1.2
jupyter-renderers	ms-	1.1.2025012901
vscode-jupyter-cell-tags	ms-	0.1.9
vscode-jupyter-slideshow	ms-	0.1.6
powershell	ms-	2025.3.0
test-adapter-converter	ms-	0.2.1
autodocstring	njp	0.6.1
vscode-extension-bpmn-editor	red	0.26.1
intellicode-api-usage-examples	Vis	0.2.9
vscodeintellicode	Vis	1.3.2
jinja	who	0.0.8

A/B Experiments

vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt551cf:31249598
vscod805:30301674
c4g48928:30535728
962ge761:30841072
dsvsc014:30777825
dsvsc015:30821418
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:30980852
dwnewjupytercf:31046870
pythonrstrctxt:31093868
nativeloc1:31118317
e80f6927:31120813
dwcopilot:31158714
5b1c1929:31184661
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
9064b325:31222308
copilot_t_ci:31222730
g012b348:31231168
pythoneinst12:31251391
bgtreat:31252123
c7cif404:31309980
pythonpulldiag:31287486
6gi0g917:31259950
editoredits36407:31282444
996jf627:31264550
pythonrdcb7:31268811
usemplatestapi:31297334
e6194696:31317039
jjjhb125:31275147
pythonfullctx:31296836
6518g693:31302842
pylancecolor:31288664
generatesymbolt:31280541
convertfstringf:31280702
gendocf:31280703
nes0dcc7202:31321960
923gi514:31310909
j97ad248:31306657
fd45d811:31320948
a2ijf515:31307742
convertlamdat:31319677
gce3e431:31315077

[Yoyokrazy]

Hi! Thanks for filing the issue. Are you able to provide any logs from the vscode output channels, and/or the developer tools console? Additionally, steps in consistently reproducing the issue would be greatly appreciated, as I can't current replicate this on my machine.

[bjornasm]

I have this error as well, looking at the developer tools I see the following errors using developer tools console:

log.ts:460   ERR Extension 'ms-python.vscode-pylance' wants API proposal 'mcpConfigurationProvider' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.`

log.ts:460   ERR [Extension Host] (node:17090) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `exe --trace-deprecation ...` to show where the warning was created)`

also

mainThreadExtensionService.ts:79 ExtensionError: Error in extension mtxr.sqltools: FAILED to handle event
	at ud.value (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:171:95298)
	at P.B (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:27:2373)
	at P.C (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:27:2443)
	at P.fire (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:27:2660)
	at VG.$acceptEditorPropertiesChanged (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:171:63544)
	at $5.S (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:116786)
	at $5.Q (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:116566)
	at $5.M (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:115655)
	at $5.L (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:114760)
	at ud.value (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:113557)
	at P.B (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:27:2373)
	at P.fire (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:27:2591)
	at po.fire (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:9458)
	at ud.value (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:361:3443)
	at P.B (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:27:2373)
	at P.fire (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:27:2591)
	at po.fire (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:29:9458)
	at MessagePortMain.<anonymous> (file:///snap/code/196/usr/share/code/resources/app/out/vs/workbench/api/node/extensionHostProcess.js:361:1735)
	at MessagePortMain.emit (node:events:518:28)
	at MessagePortMain._internalPort.emit (node:electron/js2c/utility_init:2:3073)

[Yoyokrazy]

Does this issue reproduce without extensions? Based on those logs alone, the issue appears to be coming from the extension side of things

If it doesn't repro with extensions disabled (indicating an extension as the root issue), you can use our extension bisect tools to narrow down the problem extension and file the issue there.

If it does repro (ie the problem is with vscode core), then reporting back here with consistent reproduction steps is going to be necessary, as I haven't been able to reproduce the issue.

[bjornasm]

Thank you @Yoyokrazy . When disabling all extensions except the "mandatory" from vscode: Pylance, Python, Python Debugger, Jupyter I get the initial problem of cells stopping to give output, especially when erroring (doing print ("test") for instance doesn't output anything). After an error right now I got the same popup "The window is not responding". Curiously, I get these problems when working with Duckdb in jupyter notebook, without knowing if that is related.

[Yoyokrazy]

Just double checking, you're saying that you have disabled all possible extensions and it still repro's? An easy way to ensure this is the way you've launched is with code-insiders --disable-extensions.

Regardless, next time you see this error could you do the following:

• attach all error logs from the output channels
• the following chunk:

1. Run the command node -e "process.kill($pid, 'SIGUSR1')"; lsof -i TCP | grep -E "\b$pid\b"; from terminal. Replace $pid with the pid of the extension host you want to debug
2. Open localhost:<port>/json from any chromium based browser, replace with the value that got printed in the above command
3. Copy the value of devtoolsFrontendUrl from the resulting web page and open a new tab in the browser with that url
4. You will now have a devtools session connected to the extension host process, visit the performance tab and start profiling. Stop the profile after a 10-20s or if the window becomes responsive again.

[Yoyokrazy]

Additionally, this is another set of steps that you can take to collect logs for us, thank you!
https://github.com/microsoft/vscode/wiki/Runtime-debugging#cpu-profiling-unresponsive-window-via-tracing

[Yoyokrazy]

going to close this as a duplicate of #251731

seems to be the same root cause and issue. Please open a new issue and reference this one if after the fix is applied you are still experiencing this.

Note -- the fix will land in insiders sooner than stable, since stable will need to go through the full recovery process.