Vscode-spell-checker: Spawns too many "find" processes

[ypresto]

I have no idea why but this extension spawns one find process per second in my environment.

Reproduced when disabling all other extensions, not reproduced when disabling this extension.

(Mac OS X 10.12.6, VSCode 1.16.1)

[madlou]

Not sure if its related, but since today, vscode uses 100% of my cpu, unless I disable this extension.

(Win7 64bit, 1.16.1)

[BillDenton]

Any update on this issue? This is making the extension unusable.

[Jason3S]

Thank you. I'm pushing out a fix now.

[madlou]

That’s great, thanks for the quick turnaround- really appreciate all the work you put in on the extension- it’s really useful.

[Jason3S]

I was using a VS Code method to find the settings files. apparently it is VERY inefficient. It launches all the find commands.

I have turned off the code that searches for the local config.

[ypresto]

Thanks!!

I was using a VS Code method to find the settings files. apparently it is VERY inefficient. It launches all the find commands.

Could you tell me which method it is? It might be vscode-side performance issue.

[madlou]

Could you tell me which method it is? It might be vscode-side performance issue.

Looking at his first commit for the fix, I assume the issue was with:

vscode.workspace.findFiles(findConfig, '{**/node_modules,**/.git}');

[Jason3S]

The original change went in to work around an issue with: workspace.createFileSystemWatcher(configFileWatcherGlob);
I was getting complaints about performance when someone opened vscode on a large project.

So, I switched to a polling method using workspace.findFiles. This proved to be even worse.

The final solution was to poll for the existence of explicit files and set watchers on them.