supabase start local dev is throwing segmentation fault

[shuurai]

Describe the bug When starting local development stack with 'npx supabase start', supabase_studio and supabase_pg_meta both runs, and exists immediately after with "exit 139" segmentation fault in the log of docker's inspection when testing with the --no-health-check flag. In the default command, the stack fails to start. The other services such as postgres are running okay. This is tested on a new init project.

This is only failing on my mac intel machine (works fine on my mac m2 max).

To Reproduce Steps to reproduce the behavior:

1. npx supabase init
2. npx supabase start

Expected behavior The stack should run normally, printing out the stack's details such as urls, keys, etc.

Screenshots If applicable, add screenshots to help explain your problem.

System information Rerun the failing command with --create-ticket flag.

• Ticket ID: b7e167ea87a64b03af0731d4c64ed060
• Version of OS: Ventura 13.6
• Version of Docker: v4.41.2
• Versions of Supabase cli: v2.23.4
• Services:
• public.ecr.aws/supabase/studio 2025.05.19-sha-3487831
• public.ecr.aws/supabase/postgres-meta v0.89.0

Additional context If applicable, add any other context about the problem here.

• I did install a new 16GB ram , but the computer seems to be running fine.

[ralberts]

Mac i7 Intel Version of OS: 15.4.1 (24E263) Supabase cli: v2.23.4 Docker: v4.41.2

Same here:

"Health": {
			"Status": "unhealthy",
			"FailingStreak": 0,
			"Log": [
				{
					"Start": "2025-06-01T23:47:33.013766542Z",
					"End": "2025-06-01T23:47:33.133005252Z",
					"ExitCode": 139,
					"Output": "Segmentation fault\n"
				},
			        ....

[Nacir1i]

Im running into the same issue

[kev1n]

Same issue, but with M1 Pro chip, all services except for studio are running. Studio keeps restarting with 139 exit code