-
Notifications
You must be signed in to change notification settings - Fork 659
🐛 rome is insatiable when it comes to CPU resources on windows #4422
Comments
It would be useful to have more information, for example:
|
|
I don't have a Windows OS, so I can't tell where its temporary folder is. I found this on Google: https://answers.microsoft.com/en-us/windows/forum/all/where-is-the-temporary-folder/44a039a5-45ba-48dd-84db-fd700e54fd56 Here's a brief explanation of where to find the logs: https://rustdocs.rome.tools/rome_cli/index.html#logs |
ok, those files are quite bulky.
is it supposed to do that? Or do I have to explicitly tell rome to ignore apart from that I can see that rome fails to read
here's my config:
|
I think I know how to replicate it.
I was also able to replicate it with JS files:
In the logs there's a huge output of the whole
|
That's a bug in the code that I just noticed. You should not see that warning :) the file is correct, and Rome didn't detect errors! Thank you for the thorough information!
The path coming from this event is weird 🤔 I will have to look at that. From the logs and your info it seems that you also installed rome via a package manager. That wasn't clear from your report because you didn't attach the |
I replaced my actual path like Yes, I also run What I also noticed is that when I install |
Almost definitely related to #4184 |
unlikely, the behaviour I described does not appear in 11.0, but only in 12.0. Although, I must admit this is not the only issue with CPU usage I've had, and one of them is similar to your case. |
Environment information
What happened?
on a rather small JS file (around 2 KB) it can randomly hang and start eating CPU time, probably there's an infinite loop somewhere or something similar.
This also happens on any other file extensions.
Expected result
rome should not be consuming 5% of a
12th Gen Intel(R) Core(TM) i9-12900K 3.20 GHz
processor to format a 2 KB javascript file forever/until it is killed/file is closed.Code of Conduct
The text was updated successfully, but these errors were encountered: