Closed whateverforever closed 1 year ago
Thanks for the issue. It looks like there's two things going on here.
1) We're taking a long time to analyze the dataset.py file. Not sure why. If you could share that code or provide a file that repros the problem, that would make it possible for us to possibly fix what is taking so long.
2) Something else is writing to that file. Not sure what that might be, but some other process is probably touching that file. You might try something like this: https://github.com/Sysinternals/ProcMon-for-Linux to see what is writing to that file. Additionally it might be another VS code extension. Perhaps you can try again with just the Python and the Pylance extension installed?
I second a variant of this problem on Mac M2. Ever since the latest VScode release Version: 1.78.0 my Pylance is constantly trying to analyze 20 often 40 files at a time that are apparently "open". I am running Python 3.11 and have almost completely removed all extensions. When I removed Pylance its works like a dream as soon as I add it back my editor is so slow and buggy that it has become impossible to do any work. What can I provide to debug this?
@alexlatif it would be best if you opened a new issue. Please follow the directions here:
https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue
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.
Hi there,
thank you for this powerful tool! However, I routinely have to kill the pylance plugin, as it consumes either too much CPU or too much memory. In this case, it was memory (3-4 GB, which is a lot on my 16GB machine). I noticed that it is constantly repeating "long operations", without there being any changes to the files involved. Maybe this is relevant?
Environment data
Linux <hostname> 5.8.0-63-generic #71~20.04.1-Ubuntu SMP Thu Jul 15 17:46:08 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux
Logs
Logs around the moment of the problem:
Trace log after setting TRACE and reloading vscode window is attached: 2023-04-12_pylance-bugreport.log