-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Compilation error signal: 9, sigkill: kill #100164
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
Perhaps the compiler is running out of memory and getting killed by the OOM killer. |
I monitored the memory usage. It should not be. My memory is 32g, basically free |
Can you upload a single rust file that fails to compile on your system? You can use https://gist.github.com/ as a pastebin. |
Sorry, the project is too big to be separated |
Can you get a backtrace to this by running the build under gdb then running |
I can easily imagine this compilation using 32 GB or more, question is why |
You should check dmesg and journal if there are any mentions of killed process. |
I mean... I'm not exactly surprised that Rustc is taking more than 32 gigabytes of memory to compile 30000 patterns in a single match statement. |
Why need 30000 patterns in a single match.Because I can't find a suitable way for the following modes:
|
geez the code size will probably be huge with that as well 😰 @Amdahl-rs |
And also where is the |
Thanks: @Seppel3210 |
How to compile rust on old notebook? it seems each time I compile rust-based project it always get killed (I tried to build paru) |
@RealYukiSan pass |
Thanks I will try it :3 EDIT: EDIT 2:
|
**
I have a function with 30000 enum match items, which directly reports an error when compiling. "(signal: 9, sigkill: kill)", and the code is roughly as follows
process didn't exit successfully:
rustc ................................. (signal: 9, sigkill: kill)
Meta
rustc --version --verbose
:Linux 5.15.0-41-generic #44~20.04.1-Ubuntu SMP Fri Jun 24 13:27:29 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux
Machine memory 32G
Backtrace
The text was updated successfully, but these errors were encountered: