Editor becomes unresponsive and slow after few minutes

Issue Type: Performance Issue

Open a Jupyter Notebook, after few minutes the editor slow down eating all the cpu (and filling the log files).

Extension version: 2022.2.1030672458 VS Code version: Code 1.65.2 (c722ca6c7eed3d7987c0d5c3df5c45f6b15e77d1, 2022-03-10T15:36:26.048Z) OS version: Linux x64 5.13.0-39-generic Restricted Mode: No

System Info

Item	Value
CPUs	Intel® Core™ i7-10510U CPU @ 1.80GHz (8 x 2300)
GPU Status	2d_canvas: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off opengl: enabled_on rasterization: disabled_software skia_renderer: enabled_on video_decode: disabled_software vulkan: disabled_off webgl: enabled webgl2: enabled
Load (avg)	4, 4, 3
Memory (System)	31.15GB (12.10GB free)
Process Argv	–verbose . --enable-proposed-api genuitecllc.codetogether --crash-reporter-id b7a8e658-5841-410c-b238-68977988cc60
Screen Reader	no
VM	0%
DESKTOP_SESSION	ubuntu
XDG_CURRENT_DESKTOP	Unity
XDG_SESSION_DESKTOP	ubuntu
XDG_SESSION_TYPE	x11

Process Info

CPU %	Mem MB	   PID	Process
   15	   191	 16059	code main
    0	    32	 16062	   zygote
    0	   128	 16094	     gpu-process
    0	    32	 16063	   zygote
    0	     0	 16065	     zygote
    0	   128	 16235	       window (undefined)
    0	    64	 25399	       issue-reporter
    0	    32	 16106	   utility-network-service
   15	  1021	 16122	   window (● MergeExperiments.ipynb - mass-match - Visual Studio Code)
    2	   447	 16145	   extensionHost
    0	    96	 16285	     /usr/share/code/code --ms-enable-electron-run-as-node /home/santini/.vscode/extensions/ms-python.vscode-pylance-2022.3.4/dist/server.bundle.js --cancellationReceive=file:9b222e972ace3452a5129ace741c69fcfa5ccf0ac5 --node-ipc --clientProcessId=16145
    0	   255	 16296	     /usr/share/code/code --ms-enable-electron-run-as-node /home/santini/.vscode/extensions/ms-python.vscode-pylance-2022.3.4/dist/server.bundle.js --cancellationReceive=file:17ab41539c71b44ad99ada987417066175193234c0 --node-ipc --clientProcessId=16145
    0	   415	 16497	     electron_node cChUxTSLrinx.js 
    7	   191	 16531	     /usr/share/code/code --ms-enable-electron-run-as-node /usr/share/code/resources/app/extensions/json-language-features/server/dist/node/jsonServerMain --node-ipc --clientProcessId=16145
    5	   287	 16631	     /usr/share/code/code --ms-enable-electron-run-as-node /home/santini/.vscode/extensions/ms-python.vscode-pylance-2022.3.4/dist/server.bundle.js --cancellationReceive=file:64c6d7356ab68093ada685e91cd688af4fba9110d2 --node-ipc --clientProcessId=16145
    0	   159	 16190	   shared-process
    0	    64	 16207	     ptyHost
    0	    64	 16256	     fileWatcher
    0	     0	 25418	     /bin/sh -c /usr/bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=
    0	     0	 25419	       /usr/bin/ps -ax -o pid=,ppid=,pcpu=,pmem=,command=

Workspace Info

|  Window (● MergeExperiments.ipynb - mass-match - Visual Studio Code)
|    Folder (mass-match): 5 files
|      File types: ipynb(3) txt(1) py(1)
|      Conf files:;

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593:30376534
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
vsclayoutctrt:30451275
dsvsc009:30452663
pythonvsnew555:30457759
vscscmwlcmt:30438805
vscgsvidc:30447482
pynewfile477:30463512

[IanMatthewHuff]

@mapio Per this comment here: https://github.com/microsoft/pylance-release/issues/2530#issuecomment-1088395470

I’m going to close this bug as it looks best addressed by the pylance team. If it’s not a pylance specific issue just comment back here and I can reactivate.

[mapio]

I’m not sure where this comes from. Here is the situation

the bug is making the editor unusable. I like vscode so much that I’m promoting it with all the students and colleagues I meet; this time though, I’m about to abandon it at least until the bug is fixed.

I’m more than willing to provide any info (dump, logs…). Tell me what is needed and I’ll try to comply.

It’s very hard, on the other hand, to provide a minimum viable reproducibility test case, due to the fact that the problem arises, albeit regularly, after few tens of minutes of work on large files.

I’ve reported some other information here https://github.com/microsoft/pylance-release/issues/2530