Runaway memory leak when viewing any file importing `ndarray`

[decahedron1]

rust-analyzer version: rust-analyzer version: 0.4.2594-standalone (870cb3329b 2025-08-25)

rustc version: rustc 1.91.0-nightly (523d3999d 2025-08-30)

editor or extension: VSCode, extension version 0.4.2594

relevant settings:

# User settings:
{
    "rust-analyzer.cargo.targetDir": true
}

# Workspace settings (in .vscode/settings.json):
{
    "rust-analyzer.check.command": "clippy",
    "rust-analyzer.rustfmt.extraArgs": [ "+nightly" ],
    "rust-analyzer.cachePriming.enable": true,
    "rust-analyzer.diagnostics.experimental.enable": true,
    "rust-analyzer.showUnlinkedFileNotification": false
}

repository link: https://github.com/pykeio/ort

Reproduction

1. git clone https://github.com/pykeio/ort
2. Open ort in VS Code
   • Once rust-analyzer is done priming cache, memory usage is fine.
   • Opening most files in src/ shows normal memory usage as well.
3. Open any of these affected files:
   • tests/mnist.rs
   • tests/squeezenet.rs
   • tests/upsample.rs
   • tests/vectorizer.rs
   • src/tensor/ndarray.rs
4. Observe RAM explode

Seems to have been introduced in v0.4.2586. v0.4.2579 and earlier are unaffected.

[ChayimFriedman2]

That's the next solver, of course. I'm not sure there is a real leak but we'll need to check that.

[zerocom38]

It's a huge problem for me right now. Even opening a file that imports a file that has the ndarray dependency starts to raise the memory usage dramatically. After a couple of minutes, Rust-analyzer uses more than 50GB of RAM and is constantly increasing.
Same behavior on MacOS and Windows.

Also, note that the file that imports ndarray totally hangs up the Rust-analyzer. No more annotations or refactorings. A "view mir" hangs forever.

[ShoyuVanilla]

I guess our Elaboratable implementation on next-solver might be buggy and causing infinite loop. Might be fixed soon(maybe tomorrow) but I'm gonna sleep for now 💤