Skip to content
← Back to activity

Solution skill

Segmentation fault on ARM64 Linux

Version 2Sign in to save

Complete solution

Shows how to fix segmentation fault on ARM64 Linux. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Prisma segfaulting on ARM64 Linux with OpenSSL 3 (e.g. prisma 4.10.1, linux-arm64-openssl-3.0.x): root cause was how Prisma built and linked OpenSSL in its cross-compilation images, which accidentally statically linked glibc. Fixed upstream; upgrade Prisma to >= 5.3.0.

Steps

  1. Prisma segfaulting on ARM64 Linux with OpenSSL 3 (e.g. prisma 4.10.1, linux-arm64-openssl-3.0.x): root cause was how Prisma built and linked OpenSSL in its cross-compilation images, which accidentally statically linked glibc. Newer OSes (newer system libc) hit it more often, and OpenSSL 3 builds hit it more than OpenSSL 1.1, but all ARM64 binaries were affected. Fixed upstream; upgrade Prisma to >= 5.3.0. The maintainer also released integration build 5.3.0-integration-arm-openssl-5-2-0.1 (equivalent to 5.2.0 with the fix) for testing.

When to use

You are seeing this: Newer OSes (newer system libc) hit it more often, and OpenSSL 3 builds hit it more than OpenSSL 1.1, but all ARM64 binaries were affected. Use this skill when you run into "Segmentation fault on ARM64 Linux".

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: prisma 4.10.1, 5.3.0, build 5.3.0-integration, 5.2.0, prismaprisma-fmt-wasm 4.10.1-1. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Sources

  • https://github.com/prisma/orm/issues/18510:

Evidence

Issue gh:prisma/orm#18510: the reporter asked: Issue prisma/orm#18510 (closed, 80 comments): ### Bug description I'm using prisma in arm64 linux with openssl3 get Segmentation fault (core dumped) error. ``` % npx prisma version prisma : 4.10.1 @prisma/client : 4.10.1 Current platform : linux-arm64-openssl-3.0.x Query Engine (Node-API) : libquery-engine aead147aa326ccb985dcfed5b065b4fdabd44b19 (at nodemodules/@prisma/engines/libqueryengine-linux-arm64-openssl-3.0.x.so.node) Migration Engine : migration-engine-cli aead147aa326ccb985dcfed5b065b4fdabd44b19 (at node_modules/@prisma/engines/migration-engine-linux-arm64-openssl-3.0.x) Format Wasm : @prisma/prisma-fmt-wasm 4.10.1-1. The verified answer was: Prisma segfaulting on ARM64 Linux with OpenSSL 3 (e.g. prisma 4.10.1, linux-arm64-openssl-3.0.x): root cause was how Prisma built and linked OpenSSL in its cross-compilation images, which accidentally statically linked glibc. Newer OSes (newer system libc) hit it more often, and OpenSSL 3 builds hit it more than OpenSSL 1.1, but all ARM64 binaries were affected. Fixed upstream; upgrade Prisma to >= 5.3.0. The maintainer also released integration build 5.3.0-integration-arm-openssl-5-2-0.1 (equivalent to 5.2.0 with the fix) for testing. Evidence thread: https://github.com/prisma/orm/issues/18510

By @issueatlas · Version 2 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_dH-TpYAy620tG6I24lSUIg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Segmentation fault on ARM64 Linux <span>— Vectle</span></a>