-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Huge CPU and Memory consumption caused by design problems #4952
Comments
I can confirm, on Windows 10. After update (yesterday) of Python Language Server and/or vscode_python extension VSCode not more usable. See the disk I/O and memory consumption: The extension proceeds after VSCode start:
and this process does not stop. |
Just noted in Python output pane:
|
I am also getting the same issue as well on Windows 10. It only happens once I start debugging some code. |
It only happens when the python plugin loads the python library, which requires a lot of CPU and memory. And these information that is loaded into memory is estimated to be used for IntelliCode. |
The same problem happens today. I think it's a bug of new Python plugin just released yesterday (March 26). |
Possibly a duplicate of of this in the python language server: |
I also think that the issues area of the python plugin has a large part of similar content related to such a bug. It seems that this bug is very disturbing programming and needs to be solved urgently. ;-) |
Please add further reports and repro cases to microsoft/python-language-server#832 |
Can you kindly provide instructions to downgrade extension/language-server version until this is fixed ? This issue makes VSCode completely unusable for me as it is... |
You can switch to jedi by setting jediEnabled to true in the settings.
…On Thu, Mar 28, 2019 at 2:41 AM Nicolas Barascud ***@***.***> wrote:
Can you kindly provide instructions to downgrade extension/language-server
version until this is fixed ? This issue makes VSCode completely unusable
for me as it is...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#4952 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AConiM84H37g6mJ2jYG3bd_3O1IZNwWZks5vbI4xgaJpZM4cM9GU>
.
|
Thanks. The temporary solution you provided perfectly solved my problem. The huge memory consumption disappeared when I switched to jedi by setting jediEnabled to true in the settings. So, I think the “culprit” should be And I have a question that does Microsoft's analysis tool be added or is it set to be enabled by default in the new version in March?
|
Closing in favor of microsoft/python-language-server#832 |
Issue Type: Bug
Some questions about the python plugin encountered when building python library indexes
I strongly hope that the python plugin does not
read the information into memory in real time
when creating the python library index, butinstead saves the index file
in order to speed up the time and reduce memory overhead.The python library is really too big. Sometimes I have to wait a few minutes for writing a small amount of code.
Extension version: 2019.3.6139
VS Code version: Code 1.32.3 (a3db5be9b5c6ba46bb7555ec5d60178ecc2eaae4, 2019-03-14T23:43:35.476Z)
OS version: Windows_NT x64 10.0.17763
System Info
checker_imaging: disabled_off
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
native_gpu_memory_buffers: disabled_software
rasterization: enabled
surface_synchronization: enabled_on
video_decode: enabled
webgl: enabled
webgl2: enabled
The text was updated successfully, but these errors were encountered: