Bug: SQLPro Studio crashes when connecting to any PostgreSQL server

[brmk]

Describe the bug

SQLPro Studio crashes when attempting to connect to PostgreSQL.

This reproduces with any PostgreSQL connection I try, including SQLPro's demo PostgreSQL connection. The crash happens during connection initialization, before a normal connection error/result is returned.

I could not find an open issue matching this current PostgreSQL connection crash. I found an older similar issue (#704), but it was from 2021 and was fixed at the time.

To Reproduce

Steps to reproduce the behavior:

1. Open SQLPro Studio.
2. Create or select any PostgreSQL connection.
3. Attempt to connect.
4. The app crashes.

This also reproduces with SQLPro's demo PostgreSQL connection.

Expected behavior

SQLPro should connect successfully, or show a normal connection error if the server/settings are invalid.

Screenshots

Not applicable. I can provide the macOS crash report.

Additional details

Environment:

• Product: SQLPro Studio
• Installation source: Setapp
• App version: 2026.163
• Build: 111249
• Bundle ID: com.hankinsoft.sqlpro-studio-setapp
• Platform: macOS
• macOS version: 15.3.2 (24D81)
• Architecture: Apple Silicon / ARM64
• Device model: MacBookPro18,1

Crash summary:

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000000
Termination Reason:    Namespace SIGNAL, Code 11 Segmentation fault: 11

Crashed Thread:        18  Dispatch queue: com.apple.root.default-qos

Relevant crashing stack:

Thread 18 Crashed:
0   ???                            0x0 ???
1   libpq                          pg_vsnprintf + 72
2   libpq                          appendPQExpBufferVA + 68
3   libpq                          appendPQExpBuffer + 80
4   libpq                          emitHostIdentityInfo + 276
5   libpq                          PQconnectPoll + 1800
6   libpq                          pqConnectDBStart + 116
7   libpq                          PQconnectStart + 64
8   libpq                          PQconnectdb + 16
9   SQLProPostgresCore             -[PostgresDatabaseClient connect:sshDelegate:] + 1812
10  HSShared                       __55-[SQLProConnectionWindowController doConnect:password:]_block_invoke.359 + 244

The ARM thread state also shows a null program counter / fault address:

pc:  0x0000000000000000
far: 0x0000000000000000
esr: 0x82000006 (Instruction Abort) Translation fault

Since this reproduces with multiple PostgreSQL servers, including the demo connection, this does not appear to be server-specific. The stack suggests the crash is happening inside the bundled libpq / SQLProPostgresCore connection path while calling PQconnectdb.

Full crash log

Product

SQLPro Studio

App version

2026.163

Platform

macOS

Installation source

Setapp

[hankinsoft]

I've submitted a build that I believe will resolve this based on the stack you listed. I'm not able to reproduce (even on sample database) so I'm not exactly 1000% sure but again from the partial stack it should resolve it.

[pierredemilly]

Similar issue here, has been happening for a few days.
I have the app through Setapp.

Report below is Claude-generated as it's a bit too technical for simple me.

Environment:

• SQLPro Studio 2026.173 (build 111259), Setapp build
• macOS 14.7.6 (23H626), MacBook Pro 18,3 (M1 Pro, arm64)

Summary:
Connecting to ANY Postgres database crashes the app immediately. Happens
for every saved Postgres connection regardless of host/database. Not
connection-specific.

Already ruled out:

• psql connects fine to the same databases from the same machine
• Clean uninstall + reinstall via Setapp — no change

Crash signature (full .crash attached):

• EXC_BAD_ACCESS (SIGSEGV), KERN_INVALID_ADDRESS at 0x0, pc = 0x0
• Faulting thread crashes inside the bundled libpq.framework (17.10):

  0  ??? (0x0)
  1  libpq  pg_vsnprintf
  2  libpq  appendPQExpBufferVA
  3  libpq  appendPQExpBuffer
  4  libpq  emitHostIdentityInfo
  5  libpq  PQconnectPoll
  6  libpq  pqConnectDBStart / PQconnectStart / PQconnectdb
  7  SQLProPostgresCore  -[PostgresDatabaseClient connect:sshDelegate:]

Looks like a null function-pointer call in pg_vsnprintf while
emitHostIdentityInfo builds the host-identity string during connect.

[hankinsoft]

2026.173 should be available via Setapp now. If you get the chance, please update and see if this sorts it out for you. Cheers!

[pierredemilly]

Hey, the bug is actually happening with 2026.173 (build 111259)

[hankinsoft]

Could you possibly try the following in console.app and let me know what it returns?

# TODO: You may have to replace the path to SQLPro Studio, but this should work as a default
APP="/Applications/Setapp/SQLPro Studio.app"
/usr/libexec/PlistBuddy -c 'Print CFBundleShortVersionString' "$APP/Contents/Info.plist"
/usr/libexec/PlistBuddy -c 'Print CFBundleVersion' "$APP/Contents/Frameworks/libpq.framework/Resources/Info.plist"
strings -a "$APP/Contents/Frameworks/libpq.framework/Versions/A/libpq" | grep -c '<unspecified>'

Can you include the full latest crash from ~/Library/Logs/DiagnosticReports/?