Closed
Description
opened on Aug 31, 2023
I tried this code:
I found this code would make rustc eat more than 20 gb of memory until OOM killer stopped it
fn T<T>(x: &T::<T::<T::<T::<T::<T::<T::<x, HT::U<T::<T::<x, T::<T::<T::<T::<T::<T::<T::<T::<x, T::<T, T>>T::<x, HT::U<T::<T::<x, T::<T::<TT::<T::(<T::<T)::<x, )T>>, T>>, T::<T:T, T>>>>>, T>>, T>>>, T::<x, T::<T::<T::<>>, T
I expected to see this happen: explanation
Instead, this happened: explosion
Meta
rustc --version --verbose
:
rustc 1.74.0-nightly (59a829484 2023-08-30)
binary: rustc
commit-hash: 59a8294849358a878a72358aa6d5fe5b9d312867
commit-date: 2023-08-30
host: x86_64-unknown-linux-gnu
release: 1.74.0-nightly
LLVM version: 17.0.0
Metadata
Assignees
Labels
Category: This is a bug.Call for participation: This issue needs bisection: https://github.com/rust-lang/cargo-bisect-rustcIssue: Problems and improvements with respect to memory usage during compilation.Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.Medium priorityRelevant to the compiler team, which will review and decide on the PR/issue.Performance or correctness regression from one stable version to another.
Activity