-
Notifications
You must be signed in to change notification settings - Fork 10
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
devsense.php.ls consumes too much RAM #343
Comments
Thank you @zarulizham for reporting the issue. This is definitely a bug. Is the CPU usage high as well? (VS Code creates one process for each of your workspaces, so two processes are expected when you open two workspaces). |
@zarulizham May I ask what version you have installed? We have a pre-release, which fixes several memory issues if you want to try it (https://docs.devsense.com/en/vscode/installation#pre-release-installation). |
There is an update We'll keep improving RAM in the next updates. |
The latest release fixes the issue with the process not being terminated. |
Found the real memory leak, preparing an update today. |
Tested various versions including pre-release, this issue still exists. It's even worse running multiple instances of VS Code. If I could provide any information that would help you improve/fix this I'd be happy to help. |
@chielteuben thank you for letting us know! I appreciate your help. This is definitely a bug. The expected RAM usage for larger projects is about 500MB now (and we're going to cut this to half soon).
Thank you! |
I can replicate this behaviour instantly after opening the project. This will properly display any related information instantly, devsense.php.ls being at ~ 350MB. I can share the composer.json this monday but I can tell you what's in it from memory because it's a brand new project, it's the base Laravel 10 default composer.json with only "pestphp/pest" added. |
@chielteuben awesome! I'll try to repro the issue within a day or two - if it happens to me as well, it should be easy to fix. Thank you! |
@chielteuben thank you again, we've successfully reproduced the issue and fixed this one. Most probably, it's been causing RAM and CPU issues for all the users here. We'll be preparing update within a few hours. |
Please try the latest |
I've just tested the latest version and the issue is solved! |
@chielteuben thank you very much for testing it so quickly. I'm happy it works for you. We'll keep improving the RAM usage in the upcoming updates. If there would be anything else weird, please let me know. |
I'm using the extension on 2 different projects, one is totally fine, at 95MB but the other one sits on 3.8GB The bigger project is about 3-4 times bigger than the other one, but the RAM usage is insane, I'll will try to test if it is something specific. Update: I removed most of the code and it is still sitting on 3.8GB, even after restarting vs code, The only thing left that has a lot of code in it is the vendor and a lot of asset files (js, image, pdf etc.) |
There is a way to ignore some folders to avoid indexing log folder for example? |
@LMachucaORT yes,
|
Thanks help me a lot!. |
@neriyaco Thank you for trying our tools - May I ask if the RAM issue still happens? Most large projects we're testing sit at 1.5GB RAM. |
Yes, I solved the RAM problem, because the project got too big, but by excluding many folders that I will not be working with, the RAM consumption was cut in half. |
@LMachucaORT thank you for the update! |
Hi, after exclude some files, I did not face any memory issues anymore. |
There are two processes with devsense.php.ls consume 10GB+ RAM.
I have quit VS Code, but the processes still there. I have to Force Quit from Activity Monitor. Normal Quit did not release the processes.
Thank you.
The text was updated successfully, but these errors were encountered: