Open matklad opened 3 years ago
I confirmed that rustc prints Rust cannot catch foreign exceptions
when LLVM runs out of memory. Presumably it is raising bad_alloc
, but AFAIK rust cannot catch C++ exceptions. I'm not sure if it could be caught on the C++ side, or if there is some LLVM build option to change the oom behavior.
rust-analyzer needs about 5 to 6 GB to build with LTO. I think GitHub Actions systems have 7GB of RAM, so it may be getting close to that limit. I might suggest using 'thin' LTO which should use substantially less memory.
Assigning P-high
based on WG-prioritization discussion on Zulip and removing I-prioritize.
@rustbot modify labels -I-prioritize +P-high
Starting today, I am seeing the following error in rust-analyzer's CI
This happens on windows builders, when compiling with
--target x86_64-pc-windows-msvc
or--target aarch64-pc-windows-msvc
. The step which fails is compilation of the final binary crate. The binary is complied in--release
mode withlto=true
. I think the failure appeared after I addeddebug=1
as well.So my theory is that maybe this is just some OOM in the linker, and not a problem with rustc per se? The error message is rather unhelpful though.
The relevant CI run: https://github.com/rust-analyzer/rust-analyzer/runs/2649419225?check_suite_focus=true#step:5:330