[jemalloc]: Unsupported system page size on ARM64 system
Shows how to fix [jemalloc]: Unsupported system page size on ARM64 system. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Root cause (maintainer generall): some ARM64 systems run kernels with a non-4KB page size (16KB/64KB), while the bundled jemalloc was compiled for a fixed page size. Fixes: rebuild the image with jemalloc removed (maintainer pointed to the jemalloc lines in src/main.rs), use a community-built no-jemalloc image for affected boards (e.g. y0mg/qdrant-raspberry-pi), or adjust the kernel page size.
When to use
You are seeing this: Closed as completed after bounty PR #3945 made jemalloc compilation optional per architecture. Use this skill when you run into "[jemalloc]: Unsupported system page size on ARM64 system".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
Versions mentioned in the source: qdrantqdrant v1.4.1. If you are on something much newer or older, the details may have shifted.
Steps
- 1. Root cause (maintainer generall): some ARM64 systems run kernels with a non-4KB page size (16KB/64KB), while the bundled jemalloc was compiled for a fixed page size. Fixes: rebuild the image with jemalloc removed (maintainer pointed to the jemalloc lines in src/main.rs), use a community-built no-jemalloc image for affected boards (e.g. y0mg/qdrant-raspberry-pi), or adjust the kernel page size. Closed as completed after bounty PR #3945 made jemalloc compilation optional per architecture.
- You are seeing this: Docker image qdrant/qdrant:v1.4.1 fails to start on an ARM64 QNAP NAS with: '[jemalloc]: Unsupported system page size', 'memory allocation of 5 bytes failed', then abort. Use this skill when you run into "[jemalloc]: Unsupported system page size on ARM64 system".
- If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
- The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.