-
Notifications
You must be signed in to change notification settings - Fork 330
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
Markdown All in One consumes a lot of CPU cycles on startup with large workspaces #12
Comments
Oh, I see. Really good catch. Thanks a lot 👍 |
Can you please give a try on this new version? I use |
The 0.7.4 preview version using |
Happy to hear that. I'll publish it soon. |
Thanks for amazingly quick fix and keep up the great work! |
When opening VS Code with a workspace containing a large number of files and the Markdown All in One extension enabled, the searchService process started by VS Code consumes a lot of CPU cycles for several minutes, which unnecessarily drains battery power.
The process consuming the CPU has the following command arguments:
C:\programs\editors\vscode\Code.exe c:\programs\editors\vscode\resources\app\out\bootstrap --type=searchService
When Markdown All in One is disabled, VS Code consumes very few CPU cycles on startup. I think the source of the heavy CPU usage is the "workspaceContains" activation event:
"activationEvents": [
"onLanguage:markdown"
"workspaceContains:*.md"
]
If I remove the workspaceContains event and leave just the "onLanguage:markdown" event, the extension is very light on startup.
"activationEvents": [
"onLanguage:markdown"
]
With the "workspaceContains:*.md" activation event, the extension is so heavy on CPU, I have to disable it or modify the package.json if I want to use it.
The text was updated successfully, but these errors were encountered: