3

After limiting the number jobs in order to handle the amount of resources used by rust-analyzer it keeps using all cores so my computer ends up hanged out:

enter image description here

In addition, I've noticed that several processes continue to run even after stopping the rust-analyzer. Notably, it's these processes that are consuming all available cores:

...
/usr/lib/gcc/x86_64-linux-gnu/12/cc1plus -quite -I /home/c/rust-project/target/debug/build/wasm-opt-sys...
/usr/lib/gcc/x86_64-linux-gnu/12/cc1plus -quite -I rocksdb/include/ -I rocksdb/ -I rocksdb/third-party/gtest-1.8.1/fused-src/ -I snappy...
/usr/lib/gcc/x86_64-linux-gnu/12/cc1plus -quite -I rocksdb/include/ -I rocksdb/ -I rocksdb/third-party/gtest-1.8.1/fused-src/ -I snappy...
...

For reference, my laptop is equipped with 16 cores and has 16GB RAM.

1 Answer 1

1

I've realized that the more appropriate parameter for setting the number of jobs is "cargo.extraArgs", rather than "check.extraArgs". As of now, no cargo command will use more than the specified number of jobs.

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.