🐛 Memory leak in `biome.exe`

[Profesor08]

VS Code version

1.202.0

Extension version

3.1.0

Biome version

2.1.0

Operating system

• Windows
• macOS
• Linux

Description

Found performance issues on my PC, randomly checked task manager, and found biome.exe uses 23 GB of memory, and growing little by little. The only solution is to close all vscode instances.

20250708-1348-13.1596028.mp4

Steps to reproduce

I don't know, after restart it looks ok, but I don't know for how long

Expected behavior

To not eat all my memory and to look like

Does this issue occur when using the CLI directly?

No

Link to a minimal reproduction

No response

Logs

[eMerzh]

looks like #6797 no?

[Profesor08]

@eMerzh can't say exactly, because it happened after I had updated biome to latest version. And didn't observed something like that earlier.

Currently I'm monitoring resources, used by biome, and they are consumed in normal range. Also manualy configured files.includes

{
  "files": {
    "includes": [
      "**",
      "!**/node_modules/**",
      "!**/public/**",
      "!**/.wrangler/**",
      "!**/dist/**",
      "!**/icons/**",
      "!**/patches/**",
      "!**/*.css",
      "!**/*.scss"
    ]
  },
}

[ematipico]

Memory leaks belong to core :)

However, they are hard to reproduce, so we need users to pin point which files are causing the slowness.

[github-actions]

Hello @Profesor08, please provide a minimal reproduction. You can use one of the following options:

• Provide a link to our playground, if it's applicable.
• Provide a link to GitHub repository. To easily create a reproduction, you can use our interactive CLI via npm create @biomejs/biome-reproduction

Issues marked with S-Needs repro will be closed if they have no activity within 3 days.

[SeraNox123]

Tried to reproduce, as I'm seeing the same issue — pretty sure it's due to the lint/correctness/noPrivateImports rule. Try disabling and enabling it and testing memory usage.
Using PHPStorm 2025.1.3, Biome plugin version 1.8.1 and Biome version 2.1.1

[SeraNox123]

Those rules also cause same memory leak:
lint/correctness/noUndeclaredDependencies
lint/correctness/useImportExtensions

[Profesor08]

1. Is the node_modules folder excluded by default?
2. Will a config like "include": ["src/**/*.js"] search for files only in src?
3. Will a config like "include": ["**", "!**/*.test.js", "**/special.test.js", "!test"] exclude node_modules from the search?

[siketyan]

The scanner scans entire the project even if it's not included in the config, except a few hard-coded denylist. Files in node_modules are also scanned. Behaviour of the scanner changes by turning on any of the "project rules" - that requires a detailed module graph created by the scanner. It's possible that a specific file scanned by the scanner causes memory leak as an edge case.