-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
ICE: MemDecoder exhausted #119511
Comments
Since I don't know if it's relevant, here's a
|
Upgrading to the latest version of my crates, proc_macro2 was in there as well as syn, seemed to have corrected the error. Could also be lurking somewhere in the build cache. If you want that I suppose I can provide it somewhere. Not sure what to do with this bug now, but feel free to close it if you no longer feel it's relevant. |
@saethlin does your PR fix this? |
Hm, it looks like the problem here is that the OnDiskCache footer is off the end of the file. When that happens due to out-of-disk, people tend to notice that they are out of disk. @erikh Am I correct in assuming you had some disk space available when this crash happened? If this is an out-of-disk, it was probably "solved" by #117301 then will be actually solved by #119510. But if isn't an out-of-disk situation, this is probably an incremental compilation bug. The build directory state at the time the crash happened would be useful, but if the crash doesn't recur anymore on your end then the problematic state in the build directory is probably gone. In that case, this issue is still useful to say that something is wrong here, but that's kind of all. |
@saethlin correct, I had about 900GB free on this mountpoint at the time of compilation. |
It does also make sense that my build cache was corrupt; refreshing crates seemed to correct the issue. Maybe a truncated object write or something? Just throwing things at the wall here. Either way, my personal issue is resolved, but I figure this is probably worth keeping around for resolution on a more reasonable time frame. |
Crashes like this in incremental compilation are usually due to subtle internal things like a |
Ah, interesting. So heat death of the universe before this bug probably gets closed, eh? :) I'll leave ya to it. |
Code
I do not have a minimum verifiable example. It's hard to decipher this backtrace. However, I have erikh/megalock@daed9c0 which should demonstrate this error on 1.75.0.
EDIT: sorry, I had the url syntax wrong. That link should point at the correct commit.
Meta
rustc --version --verbose
:Error output
Backtrace
The backtrace comes from rustc itself.Just doing my part, looks like my repo did something to hose the compiler. Next steps I'm happy to help with, but the repo is probably the easiest way to investigate this independently. I'm sorry I'm not more helpful.
The text was updated successfully, but these errors were encountered: