Server process exited with code 3221225501 after 0.4.2216

[decahedron1]

rust-analyzer version: 0.4.2216-standalone (9b2e72c404 2024-12-12)

rustc version: rustc 1.85.0-nightly (4ba4ac612 2024-12-18)

editor or extension: VS Code (1.96.3 / extension 0.4.2263)

repository link (if public, optional): private :(

Since 0.4.2216-standalone (9b2e72c404 2024-12-12), one of my workspaces (inconveniently the largest and private-est) has seen rust-analyzer crashing whenever a file is saved. This workspace seems to be the only one of mine with this issue. R-A versions prior to this, like 0.4.2215-standalone (b707b5a117 2024-12-11), do not have this issue.

0.4.2216 will always spit out this error:

thread 'VfsLoader' panicked at crates\vfs-notify\src\lib.rs:94:72:
called `Result::unwrap()` on an `Err` value: RecvError
stack backtrace:

before exiting with code 3221225501 (0xC000001D, seemingly illegal instruction?).

Versions after about 0.4.2227 will forego the unwrap panic and instead just crash with the illegal instruction. Versions after about 0.4.2251 will trigger the crash on any interaction, like a hover. Most are able to start up without crashing, though. (I didn't have time to do a more precise bisect, sorry)

I was only able to get info logs from the server, as debug was too verbose and VS Code would clear the output itself. Unfortunately this didn't reveal much as there didn't appear to be any indicators of failure before Connection to server got closed. Sever will restart.; nonetheless they are available here (crash @ 87455, status code @ 89425)

[decahedron1]

It seems like ab46e97 is the faulty commit. It seems to be some kind of allocation error (maybe? I don't really know what I'm doing 😅), but I couldn't get the problem to manifest with debug-assertions = true.

Maybe this is related to notify-rs/notify#602? (which would be fixed by updating notify to 7.0)

[lnicola]

That's strange, aren't we using the client-side watcher by default?