cargo: `cargo update` hangs

I’ve tried to minimize this but I haven’t made any progress.

When I run cargo update, it seems to go forever (I let it go for 30 minutes with no output; it pegged a CPU but didn’t allocate a significant amount of memory). I’ve tried breaking into it in a debugger and it’s not always in the same place, but it’s been in jemalloc or HashMap internals. I am not low on RAM.

Here’s a gist of Cargo.toml and Cargo.lock. Cargo.toml looks weird because it was generated by cargo-outdated.

If I comment out the c_vec line in Cargo.toml, the update finishes in a couple of seconds. However, trimming down Cargo.toml and Cargo.lock to only mention c_vec also doesn’t hang. I also tried bisecting by commenting out the first half of the dependencies list, and the second half, and neither hang. So it’s some combinatorial interaction between c_vec and… some other crate(s) in the list!

About this issue

  • Original URL
  • State: closed
  • Created 8 years ago
  • Comments: 19 (10 by maintainers)

Most upvoted comments

Has this issue resurfaced? I hit this one on Mac using rustc 1.19.0 and cargo 0.20.0

For now: killed the cargo process on my workstation to proceed

rust version: rustc 1.19.0 (0ade33941 2017-07-17) binary: rustc commit-hash: 0ade339411587887bf01bcfa2e9ae4414c8900d4 commit-date: 2017-07-17 host: x86_64-apple-darwin release: 1.19.0 LLVM version: 4.0

cargo version: cargo 0.20.0 (a60d185c8 2017-07-13) release: 0.20.0 commit-hash: a60d185c878c470876e123b0e40b0ba9f3271163 commit-date: 2017-07-13

I’m closing this as a duplicate of #4066, where we’re consolidating on an effort to handle cases like this in a better way.