Bug 1723064 - LLVM ERROR: out of memory
Summary: LLVM ERROR: out of memory
Alias: None
Product: Fedora
Classification: Fedora
Component: rust
Version: 31
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Rust SIG
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: FE-ExcludeArch-x86, F-ExcludeArch-x86 ARMTracker x86Tracker
TreeView+ depends on / blocked
Reported: 2019-06-22 15:49 UTC by Igor Raits
Modified: 2020-11-24 18:40 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2020-11-24 18:40:45 UTC
Type: Bug

Attachments (Terms of Use)

Description Igor Raits 2019-06-22 15:49:30 UTC
Description of problem:

When building zola on i686, it always fails with:
BUILDSTDERR:      Running `/usr/bin/rustc --crate-name zola src/main.rs --color never --crate-type bin --emit=dep-info,link -C opt-level=3 -C lto -C codegen-units=1 -C metadata=35bf062583c842ab -C extra-filename=-35bf062583c842ab --out-dir /builddir/build/BUILD/zola-0.8.0/target/release/deps -L dependency=/builddir/build/BUILD/zola-0.8.0/target/release/deps --extern actix_files=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libactix_files-fec697cadaeaf1a2.rlib --extern actix_web=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libactix_web-653f3dd80457de5b.rlib --extern atty=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libatty-c187086d550eccb9.rlib --extern chrono=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libchrono-6ecda85aedd565e8.rlib --extern clap=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libclap-b053a5309c45adee.rlib --extern ctrlc=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libctrlc-8e184a40a5af77bb.rlib --extern errors=/builddir/build/BUILD/zola-0.8.0/target/release/deps/liberrors-8e5291a50c1c5a4d.rlib --extern front_matter=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libfront_matter-bace993b5a9a6bdd.rlib --extern lazy_static=/builddir/build/BUILD/zola-0.8.0/target/release/deps/liblazy_static-e6e48afb2e4b166a.rlib --extern notify=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libnotify-ffdcfa083f0cfd74.rlib --extern rebuild=/builddir/build/BUILD/zola-0.8.0/target/release/deps/librebuild-5bc0fd0b527bcd61.rlib --extern site=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libsite-df1f823c02c0237d.rlib --extern termcolor=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libtermcolor-4e6954201430d106.rlib --extern toml=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libtoml-aa777d2fc535ed71.rlib --extern url=/builddir/build/BUILD/zola-0.8.0/target/release/deps/liburl-a0c39024aef262d0.rlib --extern utils=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libutils-bdf733143abc1b88.rlib --extern ws=/builddir/build/BUILD/zola-0.8.0/target/release/deps/libws-322bb2ce15998ceb.rlib -Copt-level=3 -Cdebuginfo=2 -Clink-arg=-Wl,-z,relro,-z,now -Ccodegen-units=1 -L native=/builddir/build/BUILD/zola-0.8.0/target/release/build/backtrace-sys-f1f423e40ad0723d/out -L native=/builddir/build/BUILD/zola-0.8.0/target/release/build/miniz-sys-9f7f8105e76894c3/out -L native=/usr/lib -L native=/usr/lib`

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Build zola
2. Observer it going OOM

Actual results:

Expected results:
Builds fine.

Additional info:
I am not sure if this is reproducible on armv7hl, but I always cancel builds after i686 fail and arm is much slower.. So I don't know if it happens there too.

Comment 1 Igor Raits 2019-06-22 15:51:08 UTC
I'm going to exclude i686 from zola arches for now.. But given that at least 15 failures were due to this, I might drop i686 entirely from %rust_arches.

Comment 2 Igor Raits 2019-06-22 17:07:04 UTC
Ok, armv7hl has the same problem.

Comment 3 Igor Raits 2019-06-22 17:07:49 UTC
I have excluded armv7hl from zola now as well.

Comment 4 Josh Stone 2019-06-24 17:13:34 UTC
You may have to disable LTO and/or debuginfo for 32-bit platforms for this package.
(Although I'm surprised -- zola doesn't look that big...)

Comment 5 Igor Raits 2019-06-25 06:36:37 UTC
Yes, disabling LTO helped on those arches. But I think this needs some proper fix in Rust / LLVM.

Comment 6 Ben Cotton 2019-08-13 16:47:21 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 31 development cycle.
Changing version to '31'.

Comment 7 Ben Cotton 2020-11-03 15:18:35 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2020-11-24 18:40:45 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.