prisma: Segmentation fault on x86_64 Linux, for v4.13.0
Bug description
After upgrading from Prisma v4.12.0 to v4.13.0, I reproducibly encounter a Segmentation Fault when running in a docker container (as a service on Google Cloud Platform), on x86_64 / node:17-slim, communicating with PostGres (v11), using libssl version 1.1.x.
Specifically, I encounter this error when running Prisma Studio, and the front end has made any model-related request - such as its initial request for counts of all models.
A full trace, with Prisma debugging enabled, is included below (in the first comment).
This issue may be related to issue #18510 (though the architecture I’m running on is x86_64).
Expected behavior
Prisma studio v4.13.0 should not cause a Segmentation Fault, and should successfully facilitate queries, as it did in v4.12.0.
Prisma information
The segmentation fault coincides with Prisma Studio’s first attempt to field a model-related request.
Environment & setup
- OS: Debian
- Database: PostgreSQL v11
- Node.js version: 17
Prisma Version
npx prisma version:
prisma : 4.12.0
Current platform : debian-openssl-1.1.x
Query Engine (Node-API) : libquery-engine 659ef412370fa3b41cd7bf6e94587c1dfb7f67e7 (at node_modules/@prisma/engines/libquery_engine-debian-openssl-1.1.x.so.node)
Migration Engine : migration-engine-cli 659ef412370fa3b41cd7bf6e94587c1dfb7f67e7 (at node_modules/@prisma/engines/migration-engine-debian-openssl-1.1.x)
Format Wasm : @prisma/prisma-fmt-wasm 4.12.0-67.659ef412370fa3b41cd7bf6e94587c1dfb7f67e7
Default Engines Hash : 659ef412370fa3b41cd7bf6e94587c1dfb7f67e7
Studio : 0.483.0
How to reproduce
Build and deploy prisma studio as a docker-containerized service on google’s cloud run connecting to a google-cloud-hosted Postgres Db, and hit the service’s endpoint.
A segmentation fault will appear in the service’s log for Prisma v4.13.0, but not for v4.12.0.
About this issue
- Original URL
- State: closed
- Created a year ago
- Reactions: 1
- Comments: 25 (8 by maintainers)
If you are not getting any
Segmentation fault, then I think you are wrong here and should open an issue over there: https://github.com/prisma/studio I did so for you, please leave a comment that you are also affected and mention the OS: https://github.com/prisma/studio/issues/1128 (I think this could be a change in the Docker container you are using - Prisma Studio has not changed this code since Prisma 2.x)@Jolg42 - Issue resolved.
Either it was as simple as including the fix from issue #19182, or else it was a fix to the docker file (which formerly installed one version of prisma during build which was subsequently, invisibly, inaccessible when calling
npx prisma studio). Either way - glad things are working again!Closing this issue for now.
Related (for posterity): https://github.com/prisma/studio/issues/1128 https://github.com/prisma/prisma/pull/19812
I should have noted - I’m encountering this issue is with Postgres (v11), rather than SQLite.