Bug #17324: You may have encountered a bug in the Ruby interpreter or extension libraries.

• Status: Third Party's Issue
• Assignee: -
• Target version: -
• ruby -v: 2.5.8
• Backport: 2.5: UNKNOWN, 2.6: UNKNOWN, 2.7: UNKNOWN

[gundamseedw (J Wong)]

i've attached the crash report log.

im using

Rails 5.2.4.4
Puma 5.0.4
Ruby 2.5.8

[gundamseedw (J Wong)]

gundamseedw (J Wong) wrote:

i've attached the crash report log.

im using

Rails 5.2.4.4
Puma 5.0.4
Ruby 2.5.8

im using macbook pro 2019. mac os catalina 10.15.7

[jeremyevans0 (Jeremy Evans)]

• Status changed from Open to Third Party's Issue

The crash information includes:

Crashed Thread:        4  thread_pool.rb*  Dispatch queue: com.apple.security.keychain-cache-queue

From what I can find, this can be caused by attempting to access the Mac OS X keychain after fork [1], which I'm guessing is what is happening to you as you are using Puma. You could try downgrading from PostgreSQL 12 to PostgreSQL 11, that may fix it [2].

[1] https://github.com/jaraco/keyring/issues/281
[2] https://www.mail-archive.com/[e-mail]/msg12088.html

[gundamseedw (J Wong)]

gundamseedw (J Wong) wrote in #note-1:

gundamseedw (J Wong) wrote:

i've attached the crash report log.

im using

Rails 5.2.4.4
Puma 5.0.4
Ruby 2.5.8

im using macbook pro 2019. mac os catalina 10.15.7

jeremyevans0 (Jeremy Evans) wrote in #note-2:

The crash information includes:

Crashed Thread:        4  thread_pool.rb*  Dispatch queue: com.apple.security.keychain-cache-queue

From what I can find, this can be caused by attempting to access the Mac OS X keychain after fork [1], which I'm guessing is what is happening to you as you are using Puma. You could try downgrading from PostgreSQL 12 to PostgreSQL 11, that may fix it [2].

[1] https://github.com/jaraco/keyring/issues/281
[2] https://www.mail-archive.com/[e-mail]/msg12088.html

It's indeed postgres related. Thanks for the clue!

adding the below in database.yml (rails) fixed the issue
gssencmode: disable