🐛 v2.5.0 regression memory leak / infinite loop with external config

[dcog989]

Environment information

Details

❯ biome rage
CLI:
  Version:                      2.4.16
  Color support:                true

Platform:
  CPU Architecture:             x86_64
  OS:                           linux

Environment:
  BIOME_LOG_PATH:                    unset
  BIOME_LOG_PREFIX_NAME:             unset
  BIOME_LOG_LEVEL:                   unset
  BIOME_LOG_KIND:                    unset
  BIOME_CONFIG_PATH:                 unset
  BIOME_THREADS:                     unset
  BIOME_WATCHER_KIND:                unset
  BIOME_WATCHER_POLLING_INTERVAL:    unset
  NO_COLOR:                     unset
  TERM:                         xterm-256color
  JS_RUNTIME_VERSION:           unset
  JS_RUNTIME_NAME:              unset
  NODE_PACKAGE_MANAGER:         unset

Biome Configuration:
  Error:                        The configuration schema version does not match the CLI version 2.4.16
  Status:                       Loaded with errors
  Path:                         biome.json
  Formatter enabled:            true
  Linter enabled:               true
  Assist enabled:               true
  VCS enabled:                  true
  HTML full support enabled:    true

Workspace:
  Open Documents:               0

note: that is obviously from 2.4.16 as I have backed out from 2.5.0

What happened?

v2.5.0 Linux x64 binary suffers a severe memory leak/infinite loop upon initialization in Zed / LSP mode when opening a file located outside a project workspace root.

The binary continuously consumes RAM until it is terminated. Reverting to v2.4.16resolves it.

Steps to Reproduce

Run the binary in LSP proxy mode, targeting a configuration file residing in a non-project directory.

Actual Behavior

The process pins a CPU core and rapidly consumes all available system RAM until a crash/OOM event occurs.

Expected result

Zed / biome does not crash

Code of Conduct

• I agree to follow Biome's Code of Conduct

[github-actions]

✅ Organic activity

No automation signals detected in the analyzed events.

View full analysis →

_{This is an automated analysis by AgentScan}

[biome-cookie]

Hello @dcog989, 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.

[dcog989]

unable to reproduce outside of Zed editor using v2.5.0

[ematipico]

Hence why the message says to also provide a minimal repository using the package we provide.

[dcog989]

I see - that one is new to me. will attempt npm create...

[dcog989]

https://github.com/dcog989/biome-memory-leak

• Open the repo folder as your project in Zed
• move outside/test.json outside of the workspace root
• open `test.json' from outside of Zed
• biome starts scanning for several seconds while rapidly consuming memory until Zed crashes

Issue does not occur with v2.4.16, it does with v2.5.0.

[ematipico]

How do you open test.json? With another Zed window?

This seems to be expected - at least following your instructions - because I opened test.json using hx which uses my local Biome. Since I opened the file in a folder that contains many other folders, it starts scanning all of them.

[dcog989]

I'm on CachyOS / KDE - so opening from Dolphin file manager. If I open from within Zed - Ctrl-O - then the issue does not occur.

So, just to be clear: I have ~/Projects/_remote/biome-memory-leak/ as my active Zed project. I then open ~/Downloads/test.json from Dolphin which opens that file in Zed that has the memory leak project active: biome starts spinning, chewing up memory, Zed crashes.

Zed settings attached in case I have done something weird with that:

settings.json

[coalaura]

I am also experiencing what appears to be a leak. Not sure exactly when its triggered, but biome will repeatedly attempt to allocate all the available memory my system has, inevitably leading to the entire system bogging down and becoming unusable until the process is killed.

Happens on 2.5.0, windows 11, regular vs code. I've had this issue happen with almost every version since around 2.3.0

Edit: essentially like #6784