Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

node use 100% cpu when pylance is enabled #5308

Closed
pcanal opened this issue Dec 29, 2023 · 2 comments
Closed

node use 100% cpu when pylance is enabled #5308

pcanal opened this issue Dec 29, 2023 · 2 comments
Assignees
Labels
perf waiting for user response Requires more information from user

Comments

@pcanal
Copy link

pcanal commented Dec 29, 2023

Type: Bug

When pylance is enabled, the remote server is using 100% cpu running the process node. When node is killed is respawns and restart taking 100% cpu.

Extension version: 2023.12.1
VS Code version: Code 1.85.1 (Universal) (0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2, 2023-12-13T09:48:06.308Z)
OS version: Darwin arm64 22.6.0
Modes:
Connection to 'ssh-remote+rootsrv1.fnal.gov' could not be established

System Info
Item Value
CPUs Apple M2 Max (12 x 24)
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
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
Load (avg) 4, 4, 4
Memory (System) 64.00GB (0.84GB free)
Process Argv --crash-reporter-id fa98420a-3f1d-4566-bb67-b533b52498ba
Screen Reader no
VM 0%

Connection to 'ssh-remote+rootsrv1.fnal.gov' could not be established

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242:30382549
vsjup518:30340749
vshan820:30294714
vscoreces:30445986
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
py29gd2263:30899288
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
89544117:30613380
2i9eh265:30646982
showlangstatbar:30737416
962ge761:30917236
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
welcomedialogc:30910334
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixt:30902429
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
h48ei257:30885898
pythontbext0:30879054
accentitlementst:30887150
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
aa_t_chat:30882232
cp7184t:30925682

@github-actions github-actions bot added the needs repro Issue has not been reproduced yet label Dec 29, 2023
@pcanal pcanal changed the title node use 100% cpu when enabled node use 100% cpu when pylance is enabled Dec 29, 2023
@heejaechang
Copy link
Contributor

@pcanal can you provide us some repro steps to do so? perf issue, it is hard to investigate with just description.

@heejaechang heejaechang added waiting for user response Requires more information from user and removed needs repro Issue has not been reproduced yet labels Jan 8, 2024
Copy link
Contributor

github-actions bot commented Feb 8, 2024

This issue has been closed automatically because it needs more information and has not had recent activity. If the issue still persists, please reopen with the information requested. Thanks.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 8, 2024
@debonte debonte added the perf label Mar 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
perf waiting for user response Requires more information from user
Projects
None yet
Development

No branches or pull requests

3 participants