What makes rustdoc grow to a virtual size of 10T when I'm building lang/rust? Yes, you read that right. Anyway, I ripped out my localbase, bootstrapped pkg, dialog4ports, ccache, and synth. The latter now attempts to build 1446 ports. lang/rust being one of them. #FreeBSD #rust
-
-
I'm beginning to suspect memory issues. I'll know for sure when I get a chance to run memtest86+. It's strange that only Rust itself is affected and only when rustdoc is run as "rustdoc --crate-type proc-macro --help" as part of the build.
1 reply 0 retweets 0 likesShow this thread -
Good news, everyone. Switching to lang/rust-nightly turned out to be a good idea. This time rustdoc never allocated more memory than necessary. I will build lang/rust-nightly one more time to ensure this is not a fluke. Btw, this is on
#FreeBSD -CURRENT amd64 r358442.1 reply 1 retweet 1 likeShow this thread -
Replying to @TrondEndrestol
That's not unexpected, given that that file is using an unstable nightly-only API. That API is opt-in. See https://github.com/hsivonen/encoding_rs/blob/e51f4d7c792a59029738c6e4aee339d03a467fe0/Cargo.toml#L18 … and https://github.com/hsivonen/encoding_rs/blob/e51f4d7c792a59029738c6e4aee339d03a467fe0/src/lib.rs#L710-L718 …. So you might want to not opt into that.
1 reply 0 retweets 0 likes
This is also opt in when compiling ripgrep, e.g., https://github.com/BurntSushi/ripgrep/#building … --- So if your build is enabling the 'simd-accel' feature of ripgrep, then you might want to disable that.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.