We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
<jemalloc>: Unsupported system page size <jemalloc>: Unsupported system page size memory allocation of 5 bytes failed [1] 22202 abort (core dumped) uv
uv venv or any uv command.
uv venv
NixOS derivation running on raspberry Pi latest kernel with the aarch64 target.
uv --version
0.2.15 ( I think, not sure because of the error)
The text was updated successfully, but these errors were encountered:
Looks like jemalloc is not supported on that operating system e.g. home-assistant/core#105768
Home-assistant provides a DISABLE_JEMALLOC option to work-around this, we might need to do similar?
DISABLE_JEMALLOC
It looks like they also changed the page size (i.e. JEMALLOC_SYS_WITH_LG_PAGE) which may solve the issue? home-assistant/docker-base#248 and more discussion at qdrant/qdrant#3945 (comment)
JEMALLOC_SYS_WITH_LG_PAGE
Sorry, something went wrong.
This is the same problem as we had in astral-sh/ruff#3791, we can try the same mitigation (JEMALLOC_SYS_WITH_LG_PAGE=16 during build)
JEMALLOC_SYS_WITH_LG_PAGE=16
I believe we have that same mitigation in our build already @konstin.
This looks like a bug in the nixos derivation then, which doesn't set JEMALLOC_SYS_WITH_LG_PAGE=16 for the aarch64 target.
@adminy can you confirm that uv works with the official package (either from github or pypi)?
No branches or pull requests
A minimal code snippet that reproduces the bug.
uv venv
or any uv command.The current uv platform.
NixOS derivation running on raspberry Pi latest kernel with the aarch64 target.
The current uv version (
uv --version
).0.2.15 ( I think, not sure because of the error)
The text was updated successfully, but these errors were encountered: