Vscode-intelephense: Extension causes high cpu load

Created on 20 Feb 2019 · 3Comments · Source: bmewburn/vscode-intelephense

Issue Type: Performance
Extension Name: vscode-intelephense-client
Extension Version: 1.0.1
OS Version: Darwin x64 18.2.0
VSCode version: 1.31.1

bmewburn.vscode-intelephense-client-unresponsive.cpuprofile.txt

Source

ottopic

👍1

All 3 comments

Same here, on linux and it crashed the renderer in VSCodium using 90% of the CPU.

Also I think probably another huge problem for almost everyone is.
https://github.com/bmewburn/vscode-intelephense/commit/10b6e7c25e7349c9a009cf6895773b56482fdc42#diff-b9cfc7f2cdf78a7f4b91a753d10865a2

Changed all the settings, so everyone on earth who had all their vendor/random php files excluded, plus didn't want it to be trying to format and whatever else I'm sure a ton of people turned off in project and user configs ages ago and never thought to check that all the settings no longer worked.

RiFi2k on 21 Feb 2019

👍1

In my case seems that intelephense indexing is in infinte loop... at the moment 3 hours of indexing...

[Info  - 8:18:58 AM] Initialising
[Info  - 8:18:58 AM] Reading state from /Users/username/Library/Application Support/Code/User/workspaceStorage/22410ee9b035cd7ecfd224c02fafb211/bmewburn.vscode-intelephense-client/60dfce98.
[Info  - 8:18:58 AM] Initialised in 14 ms
[Info  - 8:18:58 AM] Intelephense 1.0.1
[Info  - 8:18:58 AM] Indexing started.
[Error - 11:24:18 AM] TypeError: Cannot read property 'value' of undefined
    at /Users/username/.vscode/extensions/bmewburn.vscode-intelephense-client-1.0.1/node_modules/intelephense/lib/intelephense.js:39:312591
    at C (/Users/username/.vscode/extensions/bmewburn.vscode-intelephense-client-1.0.1/node_modules/intelephense/lib/intelephense.js:39:312937)
    at /Users/username/.vscode/extensions/bmewburn.vscode-intelephense-client-1.0.1/node_modules/intelephense/lib/intelephense.js:39:298279
    at n (/Users/username/.vscode/extensions/bmewburn.vscode-intelephense-client-1.0.1/node_modules/intelephense/lib/intelephense.js:39:298301)
    at t (/Users/username/.vscode/extensions/bmewburn.vscode-intelephense-client-1.0.1/node_modules/intelephense/lib/intelephense.js:39:293074)
    at n (/Users/username/.vscode/extensions/bmewburn.vscode-intelephense-client-1.0.1/node_modules/intelephense/lib/intelephense.js:39:300855)
    at t (/Users/username/.vscode/extensions/bmewburn.vscode-intelephense-client-1.0.1/node_modules/intelephense/lib/intelephense.js:39:293074)
    at n (/Users/username/.vscode/extensions/bmewburn.vscode-intelephense-client-1.0.1/node_modules/intelephense/lib/intelephense.js:39:300855)
    at t (/Users/username/.vscode/extensions/bmewburn.vscode-intelephense-client-1.0.1/node_modules/intelephense/lib/intelephense.js:39:293074)
    at n (/Users/username/.vscode/extensions/bmewburn.vscode-intelephense-client-1.0.1/node_modules/intelephense/lib/intelephense.js:39:296727)

ottopic on 21 Feb 2019

👍1

looked like an fs sync call causing the unresponsiveness. Fixed in 1.0.2. Will close this one and track further high cpu usage in other tickets.