Closed hanvo closed 1 year ago
Yes, just run env JEMALLOC_SYS_WITH_LG_VADDR=<whatever_you_want> cargo build
.
@BusyJay -- Thank you for the advise! That seemed to do the trick. But as for the value that is set is a bit mysterious to me. Do you have an idea the methodology on how to select a number? I've dug through a few github issue threads and it seems like the 2-3 posts I've seen suggest 48. But I can't pinpoint where that value came from. Thanks again for the time!
On x86_64 (and aarch64), not all addresses are used. Typically, on x86_64, only 48 bits out of 64bits for addressing. Also check https://en.wikipedia.org/wiki/X86-64.
Thank you for your reply and explanation! Closing.
Hi,
I am not sure if this an issue that can be assisted here or not. But recently I tried to build my project in a Docker image with centos using colima on a mac. I am getting this issue while building
I was able to cross reference this with an issue that looks similar to mine here: https://github.com/jemalloc/jemalloc/issues/2318#issuecomment-1214832157
Is this something that could be applied as a workaround here in tikv-jemallocator?
I am unsure if anyone else has run into a similar issue. Below are detailed stderr output
Env: Gcc Version 7.3.1 Docker image: Centos
Thanks in advanced!