Skip to content

Extension causes high cpu load #745

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

Open
jadupl2 opened this issue May 25, 2019 · 11 comments
Open

Extension causes high cpu load #745

jadupl2 opened this issue May 25, 2019 · 11 comments

Comments

@jadupl2
Copy link

jadupl2 commented May 25, 2019

  • Issue Type: Performance
  • Extension Name: php-intellisense
  • Extension Version: 2.3.10
  • OS Version: Linux x64 3.10.0-957.12.2.el7.x86_64
  • VSCode version: 1.34.0

⚠️ Make sure to attach this file from your home-directory:
⚠️/home/jacques/felixfbecker.php-intellisense-unresponsive.cpuprofile.txt

Find more details here: https://github.com/Microsoft/vscode/wiki/Explain:-extension-causes-high-cpu-load

@sirking1991
Copy link

It looks like its spawning php and not killing (or reusing) the previous process.

@tiptronic85
Copy link

Same problem on vscode 1.36.0-insider, 99% cpu load

@adambernstein
Copy link

adambernstein commented Jun 18, 2019

This is a huge issue for me. I do a lot of workspace switching on very large projects (Drupal), and the parser re-runs every single time I switch projects:

Parsing file:///c:/Users/.../dev/vendor/composer/include_paths.php
(ad infinitum)
[Info - 10:52:39 AM] All 16427 PHP files parsed in 797 seconds. 572 MiB allocated.

That's 13 minutes of extremely high CPU usage every time I open a workspace. Additionally, it takes over the "Output" tab and causes my terminal tab to lose focus.

There needs to be a way to pause or halt the parser, or possibly cache the parsed files.

@daxter1987
Copy link

Huge issue for me too, using a MacBook Pro i9 processor.

@mtangoo
Copy link

mtangoo commented Jul 10, 2019

Seems like this extension is not maintained anymore (looks like @felixfbecker have lack of time or will to continue maintaining it) looking at need help badges on issues as well as unanswered queries. So only options are (1) someone takes over the project (forking or being added as member) and keeps maintanance (2) Move to something more maintained

I have seen Serenata being actively maintained but am not sure if there is VSCode extension. In VSCode I have switched to Intelliphense and works fine!

@felixfbecker
Copy link
Owner

@mtangoo I'll happily review a PR

@philoSurfer
Copy link

Duplicate of #465
Please search first before firing off issues people. ;-) #DoYourPart

@joeyorlando
Copy link

switch to PHP Intelephense

@mtangoo
Copy link

mtangoo commented Jun 20, 2020

@joeyorlando I switched to Serenata and is working fine!

@addykays
Copy link

Still using the PHP IntelliSense on VSCode and error persist as at this moment...

@dasginganinja
Copy link

OSX and I'm still experiencing this issue in March 2025. Will be switching extensions. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests