-
Notifications
You must be signed in to change notification settings - Fork 219
The Code Helper process constantly uses 100%-200% CPU #1056
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
Comments
having a similar issue with very high cpu usage |
Same, on ubuntu |
Output is
|
in honesty, this has been an issue for almost 2 years. I remember reporting a similar issue (exactly the same: #593) they closed it and haven't worked on it since. They refer to #444 and close that as well-- made 3 years ago. I am having similar issue with a higher end pc-- disabling / removing the plugin brought down cpu usage from 50% to 3% lol. best option here is to remove the plugin as it drastically decreases performance of other VSCode features. They understand this has been an ongoing issue for years though simply will not work on it. |
This is incredibly bizarre. I'm not sure why our LSP would be using that much CPU. Feels like its stuck in an infinite loop or something. Is there a possibility you (or anyone) can provide the project that is causing this to happen? I don't see this at all ever on our own projects and the nature of an LSP means it is incredibly difficult to debug things like this because they're so environment and project dependent. |
I think it happens when I'm not in a tailwind projects, so maybe it's stuck looking for a config file or something, that it will never find. Just guessing :) |
Same here on Ubuntu 24.04, running inside Docker, continuous 120% CPU use. I have many projects in my workspace, most of which are not tailwind-based. Attaching
Needless to say, this makes the extension unusable. |
@rustyx does this happen on the latest version of the extension? Also are you using the language server directly or doing so through VSCode? |
@rustyx also is it possible you could provide a docker container setup that reproduces this issue? |
I took a strace distribution (
There's a decent chunk of The most prevalent call after everything settles is
So, so far I'm not able to reproduce this. I'm gonna try running docker in a linux vm since fs access for a mounted volume may work a bit differently. |
syscalls look pretty similar so yeah need more information on how to reproduce this |
@thecrypticace there may be an issue with handling symlinks to parent directories. The project I work with has lots of those. I could reproduce the issue locally on Ubuntu without the use of Docker. Try opening this workspace and then navigating to a/b/c/fmt.less. |
Oh yeah there's absolutely an issue with recursive symlinks related to fast-glob — I opened an issue for reference purposes here: #1185 I think at this point I'm going to have to replace |
I think that multi-root workspace example is one of the first I've seen cause node to run out of memory though so that one is fairly useful — thanks! |
I'm aiming to get a release out with this fixed today or tomorrow 👍 |
What version of VS Code are you using?
Version: 1.93.1 (Universal)
Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40
Date: 2024-09-11T17:20:05.685Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Darwin arm64 23.6.0
What version of Tailwind CSS IntelliSense are you using?
v0.12.10
What version of Tailwind CSS are you using?
3.3.3
What package manager are you using?
yarn
What operating system are you using?
macOS
Tailwind config
VS Code settings
Describe your issue
The Code Helper process associated with this extension constantly uses 100%-200% CPU:
The text was updated successfully, but these errors were encountered: