Performanceprettier-vscode3.18.0Darwin x64 18.7.01.41.1Find more details here: https://github.com/microsoft/vscode/wiki/Explain-extension-causes-high-cpu-load
For me it's big memory usage yet.
@spencer-shadley
For me reason was that my workspace contains many projects with own prettier instances in node_modules. Therefore when I edited files in all them this extension consumed almost all resources my PC (about 7Gb memory and almost always 100% CPU). But then I installed prettier globally, I've set Prettier Path to it and then all became work very well. Now VSCode consumes about 1Gb memory and there isn't more the high cpu load.
See #1135. I think this proposal would fix this problem for large repos.
I'm still seeing this issue.
esbenp.prettier-vscode-unresponsive.cpuprofile.txt
Version: 1.45.1
Commit: 5763d909d5f12fe19f215cbfdd29a91c0fa9208a
Date: 2020-05-14T08:33:47.663Z (2 wks ago)
Electron: 7.2.4
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.5.0
As an FYI, the most common reason for these perf issues is that you open a project with lots of subprojects that each have their own version of prettier. What you can do is set the prettierPath to force the extension to use a single instance of prettier for your entire project.
Something like ./node_modules/prettier will set it to always use the module at the root of your workspace.
Most helpful comment
As an FYI, the most common reason for these perf issues is that you open a project with lots of subprojects that each have their own version of prettier. What you can do is set the
prettierPathto force the extension to use a single instance of prettier for your entire project.Something like
./node_modules/prettierwill set it to always use the module at the root of your workspace.