Description
Pagefind crashes on Raspberry Pi 5 starting from version 1.5.2.
The last working version is:
- 1.5.0 → works
- 1.5.2 → crashes
The failure is caused by jemalloc failing on systems with 16KB memory
page size (Raspberry Pi OS ARM64 default).
Environment
- Device: Raspberry Pi 5 (ARM64)
- OS: Raspberry Pi OS (Linux)
- Page size: 16KB
- Node: npx / npm
Versions tested
Version Result
1.5.0 works
1.5.2 crashes
Steps to reproduce
npx pagefind@1.5.2 --site public/static --output-path public/pagefind
Error output
<jemalloc>: Unsupported system page size
memory allocation of 16 bytes failed
Expected behavior
Pagefind should run on ARM64 Linux systems regardless of memory page
size configuration (including Raspberry Pi 5 with 16KB pages).
Actual behavior
Binary crashes immediately due to jemalloc initialization failure on
16KB page size systems.
Suspected cause
- jemalloc introduced or enabled in builds starting around 1.5.1
- Raspberry Pi 5 ARM64 uses 16KB page size, incompatible with this
configuration
- 1.5.0 likely uses system allocator or different build flags
Impact
- Raspberry Pi 5
- ARM64 systems with 16KB page size
- Other non-standard Linux memory configurations
Workaround
Or run indexing on CI / local machine and deploy static output.
Request
- Provide ARM64 builds without jemalloc
- Allow fallback to system allocator
- Detect 16KB page size systems
- Provide Raspberry Pi compatible build
Description
Pagefind crashes on Raspberry Pi 5 starting from version 1.5.2.
The last working version is:
The failure is caused by jemalloc failing on systems with 16KB memory
page size (Raspberry Pi OS ARM64 default).
Environment
Versions tested
Version Result
1.5.0 works
1.5.2 crashes
Steps to reproduce
Error output
Expected behavior
Pagefind should run on ARM64 Linux systems regardless of memory page
size configuration (including Raspberry Pi 5 with 16KB pages).
Actual behavior
Binary crashes immediately due to jemalloc initialization failure on
16KB page size systems.
Suspected cause
configuration
Impact
Workaround
Or run indexing on CI / local machine and deploy static output.
Request