tailwindcss-intellisense spawns ripgrep process that chews CPU on a project without Tailwindcss #986
Comments
|
Looks like Dev Container's had a similar issue that they fixed / worked around: microsoft/vscode-remote-release#9738 It's not open source (that I can see) so I don't know exactly what they did to fix it but one of the comments gave me potential ideas to go on. I'll see what I can come up with. Thanks for reporting this! |
|
Okay so a couple of questions:
You're on an NVMe SSD so I doubt drive speed is not even remotely in play here. I wonder if Docker is doing something weird with those directories that causes directory listing and/or other file operations to slow down. |
|
I think I've found something similar in my project. It's a Python data project that as part of normal operation will install tens or hundreds of node projects. There's no tailwind install or config in the project root though, is there a sensible way I can disable it? I have the plugin installed for other projects I work on 😃 |
|
i think i have a similar problem. I noticed when my laptop suddenly started crashing. When i looked into my processes: |
|
same here |
|
Same issue |
|
I have the same issue happening. On the latest version (0.12.15) when enabled, it spawns tens of If I can provide some more info to help troubleshoot the issue, please let me know how and I'll happily provide it. |
|
Same. After installing this extension and opening a (large) codebase that doesn't use Tailwind, it spawns many of the same process: The number of processes keeps growing and growing until eventually my computer becomes very unhappy. Using version |
|
So we don't spawn these processes directly. They are spawned by VSCode — likely due to registering watch patterns. But I can't think of a reason these would spawn a bunch or use 100% CPU. @BFranse @decafdennis Would it be possible to provide access to a project that reproduces the issue (even if privately via GitHub?) |
Sorry, I can't... if you have any quick pointers on how to debug, I'd be happy to try. The extension works fine in the repo where I need it, though, so for now I'm happy to just enable it on a workspace-by-workspace basis. |
Sorry, I can't. Like @decafdennis I'm happy to try and provide any info you'd need. Edit: I was writing up all my details and wanted to attach a video, and it doesn't seem to cause issues anymore now. |
|
By any chance does using the I've also seen some reports in other extensions that the ripgrep process can have problems when symlinks are involved. Could that be the case here? |
|
Note: This investigation was based on the current I just spent several hours tracking things through VSCode's source. A number of things result in a ripgrep process being spawned like searching for files in the sidebar, clicking file URLs in terminal (if my reading was correct), searching through notebooks, etc… However, the only extension APIs that eventually invoke ripgrep are:
Our extension ONLY uses After the extension starts we:
Notably, file watchers DO NOT invoke ripgrep. These are eventually handled by either Parcel Watcher or Node's built-in file system watcher. So, as far as I can tell, the only invocation of ripgrep caused by our extension is our up to two calls to The two calls we make are for these two globs
Microsoft has a wiki note specifically about excessive ripgrep CPU usage. This article seems to call out a few big causes:
SolutionIt looks like there's not a whole lot we can do solve the problem. However, we do have the ability to cancel the search if it takes too long. While I was never able to reproduce ripgrep running "forever" I have reproduced it running for several seconds on the 1000 pkg / 200k file project I mentioned above. I've opened a PR to cancel searches after ~15s in #1242. I'm hoping this will actually terminate any "stuck" processes but testing this scenario doesn't seem to be possible for me. WorkaroundsAside from the PR there are some workarounds that could potentially speed up or entirely eliminate the searches for some people: Disable following symlinks while searchingThis advice is given in the above linked wiki note. Disabling this appears to speed up ripgrep significantly in some of my tests. Add the following to your settings. This is especially important if you use PNPM and are seeing this in projects: Use the
|
What version of VS Code are you using?
What version of Tailwind CSS IntelliSense are you using?
v0.10.5
What version of Tailwind CSS are you using?
No tailwind in my current project.
What package manager are you using?
n/a
What operating system are you using?
Fedora Linux 40 with
/homeas a BTRFS subvolume on a local NVMe drive.Tailwind config
N/A
VS Code settings
{ "python.defaultInterpreterPath": "/bin/python", "workbench.startupEditor": "none", "application.shellEnvironmentResolutionTimeout": 30, "editor.minimap.enabled": false, "workbench.colorTheme": "Monokai Pro (Filter Machine)", "workbench.iconTheme": "Monokai Pro (Filter Machine) Icons", "editor.mouseWheelZoom": true, "files.trimTrailingWhitespace": true, "editor.renderWhitespace": "all", "[python]": { "editor.detectIndentation" : false, "editor.insertSpaces": true, "editor.tabSize": 4, "editor.formatOnType": true, "editor.codeActionsOnSave": { "source.fixAll": "explicit", "source.organizeImports": "explicit" }, "editor.defaultFormatter": "ms-python.black-formatter" }, "editor.multiCursorModifier": "ctrlCmd", "redhat.telemetry.enabled": false, "editor.fontSize": 20, "editor.tabSize": 2, "files.insertFinalNewline": true, "cSpell.ignoreWords": [ "vofhoa" ], "files.associations": { "*.nomad": "hcl", "*.toml": "toml", "*.ign": "json", "*.jinja": "jinja", "*.j2": "jinja-yaml", "*.bu": "jinja-yaml" }, "vs-kubernetes": { "vs-kubernetes.minikube-show-information-expiration": "2024-01-16T23:50:49.632Z", "vs-kubernetes.crd-code-completion": "disabled" }, "editor.acceptSuggestionOnEnter": "on", "editor.quickSuggestionsDelay": 50, "editor.find.autoFindInSelection": "never", "editor.autoIndent": "full", "window.closeWhenEmpty": true, "editor.emptySelectionClipboard": true, "files.encoding": "utf8", "editor.detectIndentation": true, "editor.dragAndDrop": true, "go.toolsManagement.autoUpdate": true, "editor.codeActionsOnSave": {}, "[hcl]": {}, "emeraldwalk.runonsave": { "commands": [ { "match": "\\.nomad", "cmd": "nomad fmt ${file}" } ] }, "python.terminal.activateEnvInCurrentTerminal": true, "python.analysis.fixAll": [], "terminal.integrated.sendKeybindingsToShell": true, "[jinja-html]": {}, "editor.rulers": [ 119 ], "yaml.schemas": { "https://squidfunk.github.io/mkdocs-material/schema.json": "mkdocs.yml" }, "yaml.customTags": [ "!ENV scalar", "!ENV sequence", "tag:yaml.org,2002:python/name:material.extensions.emoji.to_svg", "tag:yaml.org,2002:python/name:material.extensions.emoji.twemoji", "tag:yaml.org,2002:python/name:pymdownx.superfences.fence_code_format" ], "editor.defaultFormatter": "ms-python.black-formatter", "inference.model": "custom", "editor.formatOnSave": true, "git.openRepositoryInParentFolders": "never", "mypy.targets": [ "app" ], "docker.dockerPath": "podman", "docker.environment": { "DOCKER_HOST": "unix:///run/user/1000/podman/podman.sock" }, "settingsSync.ignoredSettings": [ "-docker.environment", "-docker.dockerPath" ], "docker.networks.groupBy": "NetworkName", "notebook.defaultFormatter": "ms-python.black-formatter", "python.REPL.sendToNativeREPL": true, "explorer.fileNesting.patterns": { "*.ts": "${capture}.js", "*.js": "${capture}.js.map, ${capture}.min.js, ${capture}.d.ts", "*.jsx": "${capture}.js", "*.tsx": "${capture}.ts", "tsconfig.json": "tsconfig.*.json", "package.json": "package-lock.json, yarn.lock, pnpm-lock.yaml, bun.lockb", "*.sqlite": "${capture}.${extname}-*", "*.db": "${capture}.${extname}-*", "*.sqlite3": "${capture}.${extname}-*", "*.db3": "${capture}.${extname}-*", "*.sdb": "${capture}.${extname}-*", "*.s3db": "${capture}.${extname}-*" } }Describe your issue
If I enable the tailwindcss-intellisense extension and launch VS Code in a project directory that does not have any TailwindCSS code (AFAIK) the extension spawns a
rgprocess that uses 1000%+ CPU.This project is an private one that I use to manage container apps on my workstation. It has a data directory that container applications like home assistant, paperless, gitea etc use as volume mounts.
Some of these projects do have
.tsand.jsfiles in this directory so maybe it is choking on watching all of those files? Maybe the extension should check for a tailwind config and only spawn thergprocess if it knows that TailwindCSS is being used in the project root?The text was updated successfully, but these errors were encountered: