-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cargo check
results in SIGSEGV: invalid memory reference
#95734
Comments
Demangled backtrace:
That last line points to |
@rustbot label -I-ICE +I-crash +A-llvm |
Rust 1.60.0 updated to LLVM 14 -- does this problem still occur? |
It happened again with Rust 1.60.0, but this time I was compiling a different (but related) project.
This time it failed in Backtrace
In both instances where the segfault happened I was running multiple builds in parallel - I wonder if this has anything to do with memory pressure? |
I'm also getting similar issues when building anything large with >100 dependencies (such as bevy, or cargo-audit). Happens for me both on Windows 10 and on WSL Ubuntu 18.04. WSL/Ubuntu:
Windows:
The issue will happen on a seemingly different, and random, crate each time. Here's an example from building a fresh cargo new crate on WSL with the bevy 0.7 added as a dependency in Cargo.toml.
I've also seen crates fail with (exit code: 0xc0000005, STATUS_ACCESS_VIOLATION) and heap corruption errors as well. I'm not an expert at this, but I'm happy to provide more information with some guidance on how to get it. |
I ran into this as well, it's happening consistently on this commit. No debuginfo but the repro on public code should help. rustc --version --verbose
Output
|
Implement should_continue in chalk-recursive This just returns `NoSolution` if it shouldn't continue, but that should already be useful to rust-analyzer. Note: Cloning of `should_continue` is a workaround to a rustc bug ([#95734](rust-lang/rust#95734))
cargo check
failed withsignal: 11, SIGSEGV: invalid memory reference
. It's the second time I've noticedcargo check
segfaulting in the last couple of weeks or so (I don't have any output from when it first happened though).Code
I'm afraid I don't have a minimal example that reproduces the issue. Also, the project that triggered the segfault is proprietary, so I'm unable to share much more context. Hopefully this issue serves as a data point, if nothing else. Feel free to close it if it's completely unactionable.
Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: