prisma studio crashes when connecting to Supabase with: 'Segmentation fault' error

Bug description

When starting prisma studio, logs in the console are okay until message ‘Prisma Studio is up on http://localhost:5555’ then crashes with msg: ’ ERROR  Command was killed with SIGSEGV (Segmentation fault): /home/xxx/.local/share/pnpm/store/v3/tmp/dlx-301926/node_modules/.bin/prisma studio

How to reproduce

Expected behavior

to see prisma studio interface when connecting to Supabase

Prisma information

I followed this guide: https://supabase.com/docs/guides/integrations/prisma the prisma migrate running well, tables are created on Supabase

Environment & setup

Linux Mint 20.3 node v17.3.1 pnpm v7.3.0

Prisma Version

V4.0

[aqrln]

Thank you for the report!

I’m closing this issue in favour of https://github.com/prisma/prisma/issues/10649 as a duplicate to consolidate them and make it easier to keep track of the issue. Please post any questions or additional details in that thread, or open a new issue if you experience a similar problem under completely different conditions (e.g., with other DBMS or operating systems).

While we are looking for the best way to fix or prevent the underlying problem, the recommended workaround for affected users is to make sure that the versions of OpenSSL used by Node.js and the system OpenSSL match:

• either by downgrading Node.js to 16.x,
• or by upgrading the operating system (or Docker image) to use OpenSSL 3 — this might be less suitable for production systems, but this is a good option if you only encounter the issue on you local machine during development.

Alternatively, if you can’t do that and you need to stay with Node.js 18 on a system with OpenSSL 1.1.x, you can switch to the binary engine in Prisma.

[ibreslauer]

@janpio v18.7.0