-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Compiling -> "thread 'coordinator' panicked" #135075
Comments
Do you get the same error with rust 1.82? |
Yes, but... as soon as i deleted target/ and re run cargo build (with 1.82) it worked. it seems to be my pc. not an error on rust. how can i remove this bug? |
Two questions:
|
Oh right... The panic message is a bit unfortunate due to #132245 I think. |
|
Running out of disk space would explain it. Though it would be better to have a proper error message. |
Yeah, the ICE message could be better, but this is unfortunately resource exhaustion. |
The error is at the bottom:
The reason we have a garbled diagnostic is that rustc implements fatal errors with unwinding, and cg_ssa has a highly custom thread pool implementation that thinks any thread unwinding is a panic. But in this case, it's not. Now as to how a cached CGU ends up missing its object file, I have no idea. |
Note I don't think this counts as generalized resource exhaustion, the incr comp system should not have finalized an incomplete session directory. It's designed to not do that. But I think this diagnostic means it did. Yeah resource exhaustion is unfixable, but we're supposed to report it, not emit an incoherent ICE or SIGBUS/SIGSEGV like LLVM does. |
Code
Meta
rustc --version --verbose
:Error output
Backtrace
The text was updated successfully, but these errors were encountered: