Skip to content

jemalloc assertion failures during rustc compilation #44152

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
RalfJung opened this issue Aug 29, 2017 · 0 comments
Closed

jemalloc assertion failures during rustc compilation #44152

RalfJung opened this issue Aug 29, 2017 · 0 comments
Labels
C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.

Comments

@RalfJung
Copy link
Member

Properly enabling jemalloc assertion leads to rustc builds failing. This is not currently caught by our CI as the debug-jemalloc option in config.toml is broken. See #43648 for some more information on this, and https://travis-ci.org/rust-lang/rust/jobs/266493535 for a failing test log:

Building rustdoc for stage2 (x86_64-unknown-linux-gnu)
[00:50:11]    Compiling bitflags v0.8.2
[00:50:11]    Compiling pulldown-cmark v0.0.14
[00:50:11]    Compiling libc v0.2.29
[00:50:11]    Compiling log v0.3.8
[00:50:11]    Compiling gcc v0.3.51
[00:50:12] <jemalloc>: /checkout/src/liballoc_jemalloc/../jemalloc/src/jemalloc.c:2654: Failed assertion: "usize == isalloc(tsd_tsdn(tsd), ptr, config_prof)"
[00:50:12] error: Could not compile `libc`.
[00:50:12] warning: build failed, waiting for other jobs to finish...
[00:50:24] error: build failed
@shepmaster shepmaster added A-build C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue. labels Sep 1, 2017
bors added a commit that referenced this issue Aug 2, 2018
enable jemalloc assertions when configured to do so

This is essentially a re-submission of the functional part of #43648. I was unable to reproduce the issue I had back then, maybe something changed somewhere to no longer trigger the assertion.

Fixes #44152
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug. T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

2 participants