JEMALLOC_SYS_WITH_LG_PAGE=16

[wrossi]

Describe the bug

Raspberry Pi 5 uses page_size =16, resulting in error:
: Unsupported system page size
memory allocation of 16 bytes failed

I've been using wstunnel on rpi4b for a while with no issues. As I tried to run the same setup on rpi5 I bump into this issue.

To Reproduce

RPI5 6.12.25+rpt-rpi-v8
download wstunnel 10.5.0
run ./wstunnel --version

Expected behavior

wstunnel to run as normal

Your wstunnel setup

setup is not the problem. running wstunnel is

./wstunnel --version
: Unsupported system page size
: Unsupported system page size
memory allocation of 16 bytes failed
Aborted

Desktop (please complete the following information):

• OS: [raspOS]
• Version [bookworm 6.12.25+rpt-rpi-v8]

Additional context
workaround: reduce page_size to 4K by forcing to load kernel8

[erebe]

Would you mind trying this binary and let me know if it works ?
I don't have a raspberryPi 5 at hand.

wstunnel-aarch64-unknown-linux-musl.zip

[wrossi]

Hi Erebe, I'm still getting the same error message. ./wstunnel --version <jemalloc>: Unsupported system page size <jemalloc>: Unsupported system page size memory allocation of 16 bytes failed Aborted with kernel8 it's working: ./wstunnel --version wstunnel-cli 10.5.0 thanks

…

On Sun, Nov 16, 2025 at 6:16 PM Erèbe - Romain Gerard < ***@***.***> wrote: *erebe* left a comment (erebe/wstunnel#470) <#470 (comment)> Would you mind trying this binary and let me know if it works ? I don't have a raspberryPi 5 at hand. wstunnel-aarch64-unknown-linux-musl.zip <https://github.com/user-attachments/files/23570025/wstunnel-aarch64-unknown-linux-musl.zip> — Reply to this email directly, view it on GitHub <#470 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACMZ5QHPKH3JJKMODWZ7X2T35C5PJAVCNFSM6AAAAACMA7DLDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTKMZZGA4DKMJUGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[erebe]

Thanks for testing, need to find a way to test it myself. I think it will take me time to get it right with github action.

In the meantime, you can compile wstunnel by hand.

[holysoles]

I ran into this as an Asahi Linux user, figured I could share a resource about 16k page size compilation: https://asahilinux.org/docs/sw/broken-software/#why-does-not-work-sometimes-mean-instantly-segfault

I'm not a rust developer, but this specific example seems relevant:

Package	Upstream Report	Notes
jemalloc	jemalloc/jemalloc#467	Upstream unwilling to fix, Needs build options if compiled on a 4k page size system. Addressed in ArchLinuxARM.

I don't mind the manual compilation though. Thanks for your work on this project!

[wrossi]

Sorry I had to return the pi5. I might get another in the new year.

…

On Sun, 7 Dec 2025, 23:39 Patrick Evans, ***@***.***> wrote: *holysoles* left a comment (erebe/wstunnel#470) <#470 (comment)> I ran into this as an Asahi Linux user, figured I could share a resource about 16k page size compilation: https://asahilinux.org/docs/sw/broken-software/#why-does-not-work-sometimes-mean-instantly-segfault I'm not a rust developer, but this specific example seems relevant: Package Upstream Report Notes jemalloc jemalloc/jemalloc#467 <jemalloc/jemalloc#467> Upstream unwilling to fix, Needs build options if compiled on a 4k page size system. Addressed in ArchLinuxARM <archlinuxarm/PKGBUILDs#1914>. I don't mind the manual compilation though. Thanks for your work on this project! — Reply to this email directly, view it on GitHub <#470 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACMZ5QETRAEZ3CPHMHTKMLT4AS3DJAVCNFSM6AAAAACMA7DLDWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMRTG44TENBUGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>