rome/tools

馃悰VSCode extension stuck at 100% cpu usage

Open

#4,184 opened on Jan 31, 2023

View on GitHub
聽(38 comments)聽(0 reactions)聽(1 assignee)Rust聽(23,438 stars)聽(647 forks)batch import
A-LSPHelp wantedS-Needs info

Description

Environment information

same Rome rage as here

https://github.com/rome/tools/issues/4182#issuecomment-1410177376

too big to paste in this issue creation page for some reason

What happened?

After working for a while, saving a file gets stuck and these kinds of messages appear, spinning indefinitely:

If I look at how Rome is doing in the activity monitor, it's stuck spinning at 100% like so:

Seems like there's an infinite loop issue happening? Not sure what else it could be.

If I just dismiss the dialogs, I notice that the Rome process continues to be maxed out, looks like it's stuck. Only way to stop is either close vscode or kill the process directly.

Expected result

Rome not cause CPU to max out at 100% forever!

Code of Conduct

  • I agree to follow Rome's Code of Conduct

Contributor guide

Tech stack
rusttypescript
Domain
developer experience
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
Rust programmingVSCode extension architectureRome LSP internalsDebugging infinite loops
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
10
Research direction
The issue describes the Rome extension causing 100% CPU usage after saving files, suggesting an infinite loop in the Rome process. This is likely in the LSP server component written in Rust. To debug, start by attaching a debugger to the Rome server process or adding logging to file save handling. Check the referenced issue (#4182) for more context. The maintainers have not yet identified the root cause. Focus on the text document sync logic and any recent commits that might have introduced the bug.