Date: Mon, 13 Sep 2021 00:32:16 +0000 From: bugzilla-noreply@freebsd.org To: gecko@FreeBSD.org Subject: [Bug 257419] lang/rust: panic on armv7 at 'capacity overflow', library/alloc/src/raw_vec.rs:546:5 Message-ID: <bug-257419-21738-3ku48bIr5D@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-257419-21738@https.bugs.freebsd.org/bugzilla/> References: <bug-257419-21738@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257419 --- Comment #21 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Jan Beich from comment #4) So far every example that I've seen in the ongpoing bulk -a I've got in process is doing (via an example: cargo-c): | `-- /usr/bin/make -C /usr/ports/devel/cargo-c build | `-- /usr/local/bin/cargo build --manifest-path /wrkdirs/usr/ports/devel/cargo-c/work/cargo-c-0.9.2+cargo-0.55/C | `-- /usr/local/bin/rustc --crate-name im_rc --edition=3D2018=20 There can be multiple cargo subprocess instead of just one /usr/local/bin/r= ustc . The process getting the huge CPU time is the one running /usr/local/bin/car= go . For example: 342:31.37 /usr/local/bin/cargo . . . 33:21.39 /usr/local/bin/rustc . . . Given the (effectively unbounded?) number of messages about pthread_peekjoi= n_np that seem to be accumulating in the log files, the problem may be tied to c= argo vs. its subprocesses. --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257419-21738-3ku48bIr5D>