Current-Users archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: new jemalloc vs VirtualBox

In article <>,
K. Schreiner <> wrote:
>I've had " ... distribution" failing on an amd64-VM running in
>VirtualBox (newest test version) like so:
><jemalloc>: /u/NetBSD/src/external/bsd/jemalloc/lib/../dist/src/arena.c:647:
>Failed assertion: "nstime_compa\ re(&decay->epoch, &time) <= 0"
>[1]   Abort trap (core dumped) /u/NetBSD/arch/amd64/TOOLS/bin/nbmake _THISDIR...
>--- obj-ln ---
>*** [obj-ln] Error code 134
>nbmake[3]: stopped in /u/NetBSD/src/bin
>1 error
>Reason seems to be time "going backwards" what new jemalloc doesn't like.
>After adding
>      VBoxManage setextradata "VM name" "VBoxInternal/TM/TSCTiedToExecution" 1
>to the amd64-VM definiton, the problem seems to be gone.
>Have others seen this perhaps?

Yes, I have and it seems to be indeed time going backwards. Perhaps I should
disable this test, and leave debugging on until we cleanup all the issues it


Home | Main Index | Thread Index | Old Index