high Memory Usage (again)

[cottrell]

Is this high memory usage expected? Is vscode collecting informatino about this? I feel like I've filled out quite a few feedback surveys. Is there something to switch to for python? Main thing we need is click through to definition.

[MikhailArkhipov]

There should not be that many instances unless you have multiroot workspace with that many roots.

[jakebailey]

The screenshot is from htop with threads shown (green lines); the above are threads of the same process.

[cottrell]

Yes, I should have mentioned that. There is only one process but with many threads (which I am not worried about). It's about 12G virtual and over 5G resident. It could be just that it is traversing many python librariers. But the way I use vscode this will always happen if it goes deep enough into my library. I'm guessing it is building some kind of index on the fly without spilling anything to disk? I'm not quit clear on what it would be holding in memory that is beyond what a normal IPython session would hold (which I also run important much of the same code).

[jakebailey]

You used the question form; our bug form asks for a bunch more info that we'd need to figure out anything about what's going on. I suggest providing that info, which is mirrored here: https://github.com/microsoft/python-language-server/blob/master/TROUBLESHOOTING.md#filing-an-issue

[MikhailArkhipov]

Still a bit odd there are that many threads unless analysis is still in progress and even then it should be limited to number of CPUs.

[jakebailey]

As far as I know, this has sorta been the case for a while. For example, see the screenshot in #1755. IIRC we only limit the number of tasks, and to a multiple of the CPU count, but I don't think we're directly limiting the thread count anywhere unless I've missed something.

[CMLL]

The screens in that issue are from an issue I currently have with a couple of files that seems related to a circular import going on between the 2 of them. If I open other project or other files in the same project the LS never goes extremely high in memory usage or thread count, but opening these files, there are 3 of them haven't been able to determine if is a combination of them or simply one of them, makes my memory go high, thread count to spike, LS to become not responsive and sticks around after I close the VSCode client until I forcefully kill it.

[jakebailey]

Right; I was just referring to the htop screenshot, not necessarily that they're related.

[CMLL]

From the issue screenshot and what I see on my end it could def be related. But that's just a theory.

[MikhailArkhipov]

#1460 ?

[WilliamStone]

Memory leak.

• PC physical memory is 32G.
• never explicitly opened any .py file in VSCode since windows restart.
• VSCode opened for a few days.
• This memory leak is first time to appear in my PC.

System: Windows10 2004
VSCode About Information:

Version: 1.46.0-insider (user setup)
Commit: 2591ede95a52400d5d22989b16706f9b8b4831da
Date: 2020-05-22T21:13:15.709Z
Electron: 8.3.0
Chrome: 80.0.3987.165
Node.js: 12.13.0
V8: 8.0.426.27-electron.0
OS: Windows_NT x64 10.0.19635

[koliyo]

I have similar experience. Definitely some kind of leak. Leaving an VS Code session open, but untouched over night or after some days can cause the whole computer to become unresponsive.

Running on Mac OS
We have a large Python API wrapped around C++ code using SWIG.

No problem with fresh VS Code session, but deteriorates over time.

Have verified multiple occasions that Microsoft.Python.LanguageServer is what is eating all the memory.

[MikhailArkhipov]

Try

"python.analysis.downloadChannel": "beta"

see of 0.5.51 is any better.

[CMLL]

I've been using the daily channel for some time. 0.5.51 doesn't seems to have any positive impact on the issue for me.

[vj68]

On Ubuntu 18.04 also

[jakebailey]

I would consider trying out our new LS, Pylance, to see if its performance characteristics work better for you.

[mw-cyzen]

Try

"python.analysis.downloadChannel": "beta"

see of 0.5.51 is any better.

5.51 isnt any better. running on Ubuntu 18.04.3 LTS its eating my entire virtual memory space in under an hour ( 36gb ) it sits on "analyzing in background"

how do i disable?

[MikhailArkhipov]

You can try Pylance server instead. It is an extension on marketplace.

[mw-cyzen]

You can try Pylance server instead. It is an extension on marketplace.

ty, works as expected