Constantly hogs CPU (occurred in conjunction with databricks plugin)

[michstress]

Type: Performance Issue

Always occurs if ipynb is loaded, sync with databricks is enabled

Extension version: 2023.7.20
VS Code version: Code 1.80.1 (74f6148eb9ea00507ec113ec51c489d6ffb4b771, 2023-07-12T17:22:07.651Z)
OS version: Windows_NT x64 10.0.19045
Modes:

System Info

Item	Value
CPUs	Intel(R) Core(TM) i7-6820HQ CPU @ 2.70GHz (8 x 2712)
GPU Status	2d_canvas: enabled canvas_oop_rasterization: disabled_off 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 video_decode: enabled video_encode: enabled vulkan: disabled_off webgl: enabled webgl2: enabled webgpu: enabled
Load (avg)	undefined
Memory (System)	15.35GB (5.26GB free)
Process Argv	--crash-reporter-id 180d5436-1b33-4d3a-9bba-fa580d4fc6a0
Screen Reader	no
VM	0%

Process Info

CPU %	Mem MB	   PID	Process
    0	   128	 15400	code main
    0	   206	   632	window [1] (interactive.ipynb - ai_pstudio - Visual Studio Code)
    0	   120	 11360	shared-process
    0	    78	 13960	ptyHost
    0	     7	 24004	     conpty-agent
    0	    53	 24108	     C:\WINDOWS\System32\WindowsPowerShell\v1.0\powershell.exe -noexit -command "try { . \"c:\Users\MLeisener\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\contrib\terminal\browser\media\shellIntegration.ps1\" } catch {}"
    0	   199	 14792	extensionHost [1]
    0	    16	  7940	     c:\Users\MLeisener\AppData\Local\Programs\Python\Python310\python.exe c:\Users\MLeisener\.vscode\extensions\ms-toolsai.jupyter-2023.6.1101941928-win32-x64\pythonFiles\vscode_datascience_helpers\kernel_interrupt_daemon.py --ppid 14792
    0	    11	 10464	       C:\WINDOWS\system32\conhost.exe 0x4
    0	    65	  9832	     electron-nodejs (qfyVb.js )
    0	    11	 22924	       C:\WINDOWS\system32\conhost.exe 0x4
    0	   107	 13268	     electron-nodejs ("C:\Users\MLeisener\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node c:\Users\MLeisener\.vscode\extensions\visualstudioexptteam.intellicode-api-usage-examples-0.2.7\dist\server\server.js --node-ipc --clientProcessId=14792)
    0	    51	 14228	     C:\Users\MLeisener\AppData\Local\Programs\Python\Python310\python.exe c:\Users\MLeisener\.vscode\extensions\ms-python.python-2023.12.0\pythonFiles\run-jedi-language-server.py
    0	    11	 15756	       C:\WINDOWS\system32\conhost.exe 0x4
    0	    91	 25232	     electron-nodejs ("C:\Users\MLeisener\AppData\Local\Programs\Microsoft VS Code\Code.exe" --ms-enable-electron-run-as-node "c:\Users\MLeisener\AppData\Local\Programs\Microsoft VS Code\resources\app\extensions\json-language-features\server\dist\node\jsonServerMain" --node-ipc --clientProcessId=14792)
    0	    50	 26252	     c:\Users\MLeisener\AppData\Local\Programs\Python\Python310\python.exe c:\Users\MLeisener\.vscode\extensions\ms-python.black-formatter-2023.4.1\bundled\tool\lsp_server.py
    0	    11	 23904	       C:\WINDOWS\system32\conhost.exe 0x4
    0	    98	 15160	window [2] (Issue Reporter)
    0	    28	 18852	   crashpad-handler
    0	   112	 19520	   gpu-process
    0	    98	 19884	fileWatcher [1]
    0	    43	 22472	   utility-network-service
    0	   115	 22624	   window

Workspace Info

|  Window (interactive.ipynb - ai_pstudio - Visual Studio Code)
|    Folder (ai_pstudio): 8664 files
|      File types: py(2690) pyc(2687) pyi(1791) txt(69) pyd(64) exe(32)
|                  typed(16) h(16) html(15) dll(14)
|      Conf files: project.json(1) settings.json(1);

A/B Experiments

vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
282f8724:30602487
pyind779:30671433
f6dab269:30613381
pythonsymbol12:30671437
a9j8j154:30646983
showlangstatbar:30737416
vsctsb:30748421
pythonms35:30701012
03d35959:30757346
pythonfmttext:30731395
pythoncmv:30756943
fixshowwlkth:30771522
hideindicator:30785051
pythongtdpath:30769146
i26e3531:30792625
pythonnosm12tcf:30779713
pythonidxpt:30784022
pythonnoceb:30776495
h7j2d465:30786200
h0f32768:30792100
dsvsc013:30789517
cmakesidepanelv2:30779593

[bschnurr]

please add the trace logs. see https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue

[michstress]

could not capture the beginning, as it constantly writes to the log, guess that's part of the CPU hogging

pylance_running_wild.txt

[rchiodo]

Can you share your settings.json file? It looks like we are just trying to index a whole lot of stuff. We should have stopped after 2000 files though. Your settings may be causing us to index more stuff.

Or if you can share your repository we can try and reproduce the problem.

[michstress]

Unfortunately I cannot share the repo, but it really is a bit prototyping and maybe 2-3 self written files with less then 1000 lines

settings is quite small (c++ part is due to some failed tests, not yet removed)

{
"[python]": {
"editor.defaultFormatter": "ms-python.black-formatter"
},
"python.formatting.provider": "black",
"python.formatting.blackArgs": [
"--line-length",
"125"
],
"C_Cpp.default.cppStandard": "c++17",
"C_Cpp.default.cStandard": "c17",
"python.envFile": "${workspaceFolder}\.databricks\.databricks.env",
"databricks.python.envFile": "${workspaceFolder}/.env",
"jupyter.interactiveWindow.cellMarker.codeRegex": "^# COMMAND ----------|^# Databricks notebook source|^(#\s*%%|#\s*\<codecell\>|#\sIn\[\d?\]|#\s*In\[ \])",
"jupyter.interactiveWindow.cellMarker.default": "# COMMAND ----------",
}

[judej]

There hasn't been activity on this issue for over 2 months.

It would be helpful if you would add the information in the report as described in the troubleshooting guide? minimal sample would be useful

If you are still seeing this issue, would you please reopen the issue?

thanks