-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Tailwind CSS IntelliSense max CPU load on macOS #1109
Comments
@ChristianAgren after playing some time around, I could solve the issue by adding
to the settings.json. Hope this helps! |
up ... same here |
I have the same exact problem with Tailwind 4 - beta.8 |
Same problem here, you can easily see tailwind related processes through Edit: Happening mostly on large projects & monorepos. |
What version of VS Code are you using?
v1.96.0
What version of Tailwind CSS IntelliSense are you using?
v.0.12.16, v0.12.15, v0.12.14
What operating system are you using?
macOS Ventura 13.6
VS Code settings
Describe your issue
Starting the Tailwind CSS IntelliSense extension in VSCode (in a specific project) takes my CPU usage from ~2% to over 90%. This happens with the aforementioned extension versions. If I install an earlier version, my CPU usage is fine.
The project that I experienced the issues in does not use tailwind in itself. If I check Activity monitor, I can see that VSCode has started a bunch of processes called rg (related to file searching?)
Looking closer at these processes by running
ps aux | grep <process id>
in the terminal, they seem to refer to a bunch of other extensions (nrwl.angular-console, vscode-eslint, code-spell-checker, vscode-yaml) but I don't think they are the culprits as it's only when I start the tailwind extension that my CPU goes through the roof. One of the extensions that the processes are referring to is the json-language-features extension that comes prebundled with vscode, which I don't want to disable.The temporary fix for me right now is disabling the tailwind extension or using v0.12.13
The text was updated successfully, but these errors were encountered: