Date: Sun, 05 Apr 2020 10:40:50 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 245369] <jemalloc>: jemalloc_arena.c:647: Failed assertion: "nstime_compare(&decay->epoch, &time) <= 0" Message-ID: <bug-245369-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=245369 Bug ID: 245369 Summary: <jemalloc>: jemalloc_arena.c:647: Failed assertion: "nstime_compare(&decay->epoch, &time) <= 0" Product: Base System Version: CURRENT Hardware: amd64 OS: Any Status: New Severity: Affects Only Me Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: stevenhaocheng@163.com Here's the issue: <jemalloc>: jemalloc_arena.c:647: Failed assertion: "nstime_compare(&decay->epoch, &time) <= 0" Abort (core dumped) I got this output many many times, and I'm really upset when I see this because it usually appears when my git clone almost ends/download almost finishes/cmake configuration almost finishes. This time, I got it when I was comfiguring llvm using cmake. I had to do that work again! And it costs time! This message will just randomly pop onto my screen when I am operating my disk ("quickly and vastly", i.e. git allocating space for ENORMOUS downloads like llvm-project, or unzip extracting a zip file that is several GiB big), regardless of the command I invoked. Notes: Output of uname -a: http://mpuw-um9c5.byethost4.com/unamea.txt cmake.core core dump (compressed with xz -z9ekvv cmake.core): http://mpuw-um9c5.byethost4.com/cmake.core.xz -- You are receiving this mail because: You are the assignee for the bug.help
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-245369-227>