VS Code version

1.93.1

Extension version

2.3.0

Biome version

1.8.3

Operating system

• Windows
• macOS
• Linux

Description

Formatting takes forever, which pretty much makes extension non-responsive, i.e. it has a constant high processor usage with no results.
When trying to kill biome.js which seems to be stuck on something it will relaunch itself. Or when trying to relaunch LSP server from VSCode command prompt it will error out about Restarting client failed or Biome client: couldn't create connection to server., thus requiring a full VSCode relaunch, only for the same thing to happen again.

Steps to reproduce

1. git clone https://github.com/GabenGar/repros.git
2. cd repros/biomejs/extension-formatter-large-files-chug
3. npm install
4. code .
5. Open src/main.js and format it from the context menu
6. Observe high CPU usage and no results and therefore close the IDE
7. Run formatter from CLI npx biome format ./src/main.js with the same problem. It will say that it did format in under 2 seconds after finishing for clearly more than 2 seconds.
8. Run prettier from CLI npx prettier format ./src/main.js. It will take more than 2 seconds but less than biome formatter.
9. Run formatter but with in-place rewrite npx biome format --write ./src/main.js. This will be lightning fast, which makes me think the base formatter command is a suspect and it degrades the entire extension. Although linter invoked as npx biome lint ./src/main.js is pretty fast too, but opening said file in VSCode will spike CPU usage from extension even before formatting.

Expected behavior

Not taking forever to format (prettier extension legit does it faster with less resource usage) and allow to restart LSP server without restarting the whole IDE if things go down south.

Does this issue occur when using the CLI directly?

Yes

Link to a minimal reproduction

https://github.com/GabenGar/repros/tree/main/biomejs/extension-formatter-large-files-chug

Logs

No response