-
Notifications
You must be signed in to change notification settings - Fork 13.3k
ICE: The Rust Compiler Panicked After I Removed A Windows SDK #128275
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
Comments
I assume you've tried |
( not sure if it actually requires that, but tagging for now. ) |
Yes, I did, althought the error messages are not always the same. (I am really new with Rust here)
|
What, STATUS_ACCESS_VIOLATION? @geassed-bum Okay, so, the previous error messages you were reporting were confusing but not entirely unexpected. They're "internal compiler errors". You still shouldn't see them, but if you do, then everything is working relatively normally. The compiler identified something was wrong, and then forced itself to stop continuing. You get a backtrace, which is mostly useless to you, but is fairly useful to report back to us. But when I say "you shouldn't see |
Just to rule out a lower-likelihood but deeply confounding possibility: What CPU does this computer use? Which manufacturer (e.g. Intel? AMD?) and which model (e.g. Core i5 6400, Ryzen 7600X, etc.)? |
AMD Ryzen 7 3700X. |
13th and 14th gen intel cpu's are having stability issues that cause random crashes in various heavy workloads like compiling things. We have had several crashes reported now that are almost certainly caused by buggy hardware like this: https://github.com/rust-lang/rust/issues?q=is%3Aissue+label%3AC-defective-hardware+is%3Aclosed Because of this we nowadays often ask for the cpu that was used in case of crashes that are not easily explainable, just to make sure that it isn't defective hardware. I'm not aware of any such issues with your cpu. |
I also started getting Crash during bootstrap:
Minimized:
Backtrace:
|
Could #128498 be related? |
Sorry, I've sent the previous message too soon, I've updated it. |
I cannot reproduce this on nightly though.
Upd: I cannot reproduce the issue on Linux inside WSL on the same machine as well. Let's check what happens if I build LLVM myself instead of downloading it from CI. |
The Rust compiler worked fine on my Windows desktop computer for a while (starting with the version 1.78). One day after I removed a Windows 10 SDK from Visual Studio Installer, the rustc is never able to compile any bevy example. I tried adding one Windows 10 SDK back to my system(I cannot remember the exact version I uninstalled), the result is still failure.
My operating system is Windows 10 Professional 22H2. The only Windows SDK left on my computer is Windows 11 SDK(10.0.22621.0)
Below are the error messages I get after I tried "cargo run --example breakout" on latest trunk code of bevy code(or any other branch).
====================================================================================
The text was updated successfully, but these errors were encountered: