trail vessel
this is the third time this has happened:
build with cargo
pc slowed, no output, nothing works.
shut down pc
reboot, emergency shell.
recover steps:
fsck all partitions
chroot into system
reinstall kernel (takes ages somehow, 40m compared to normal 2m)
after the third time I noticed that this was caused by building a package with cargo (but only sometimes)
What is causing this, and how can I prevent this?
trail vessel
you build what with cargo?
my own creation
bright hound
this is the third time this has happened:
> build with cargo
> pc slowed, no out...
I don't use linux, and there are very sparse details here, but I was able to findt his post that may help you:
This StackExchange post says to increase your swap space, since if you project is massive with multiple targets, in non release mode it can take up too much ram, crashing your computer.
The other one was actually unrelated, searching more now.
trail vessel
that might be it then
I'm using a Chromebook with 4GiB
but the program is not huge or something
but I'll keep an eye on my ram counter
bright hound
Couldn't find anything more. If it continues, I would advise giving more details so the people that do use linux can effectively help. That would be things like the system logs, the thing you are building/it's dependencies, arch and kernel version, rust version, etc.
sinful fiber
I agree that this is likely not an issue specifically with Rust, rather an issue with your setup (PC/install) that is being triggered by a Rust compile. Could you share the Cargo.toml of the project?
earnest vine
this is the third time this has happened:
> build with cargo
> pc slowed, no out...
systemd times out mounting your devices. If both /boot and /home is in the same disk, that pretty much means that disk is screwed and corrupted (possibly physically and/or software-wise)
but most likely physically since I don't see how a software issue could affect 2 different partitions
⇒ your disk is most likely dead
and before you ask, this has nothing to do with rust, it's just that your system kernel failed to OOM rustc/cargo and froze itself (and most likely due to sysctl misconfigurations)
trail vessel
I agree that this is likely not an issue specifically with Rust, rather an issue...
[package]
name = "test"
version = "0.1.0"
edition = "2021"
[dependencies]
execute = "0.2.13"
rocket = "0.5.1"
serde_json = "1.0.117"
tokio = "1.38.0"
I just encountered the same problem on a different machine (server)
since that is a minimal install the bug is likely either caused by any of the core packages or the compiler
sinful fiber
Well... you're pulling in rocket, serde, and tokio, some of the largest crates in the ecosystem, so you'll definitely be running into memory issues on a 4GiB chromebook