Supabase on ARM (M1) crashes due to wrong vector system page size

[Siilwyn]

Bug report

• I confirm this is a bug with Supabase, not with my own application.
• I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Starting supabase locally (npx supabase start) sucessfully starts most services with the exception of the supabase vector service. It causes a core dump:

<jemalloc>: Unsupported system page size
memory allocation of 5 bytes failed
Aborted (core dumped)

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Start supabase locally
2. Wait for container health checks
3. See error logs

Expected behavior

Supabase vector should not crash on ARM.

System information

• OS: Asahi Linux Fedora
• Version of supabase-js: 2.67.0
• Version of Node.js: 22.21.1

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

⚠️ Possible Duplicate Issue

• Supabase self hosting on Asahi Linux (apple silicon) supabase#35900

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!