Project

General

Profile

Actions

Bug #16390

closed

Crash report for ruby2.6.4p104

Added by codinganarchy (Matthew Tanous) about 2 years ago. Updated about 2 years ago.

Status:
Third Party's Issue
Priority:
Normal
Assignee:
-
Target version:
-
ruby -v:
ruby 2.6.4p104 (2019-08-28 revision 67798) [x86_64-darwin18]
[ruby-core:96060]

Description

Hello, Ruby 2.6.4 just crashed for me while using the apartment gem to switch postgres search paths in Rails.

Attached is the console output in crash-console-output.txt, as well as the crash log ~/Library/Logs/DiagnosticReports/ruby_2019-12-02-111027_RCM-YG1H4JGH8.crash.

Please let me know if I can provide any additional information. Thanks!


Files

crash-console-output.txt (701 KB) crash-console-output.txt Console output of crash codinganarchy (Matthew Tanous), 12/02/2019 04:19 PM
ruby_2019-12-02-111027_RCM-YG1H4JGH8.crash (68.3 KB) ruby_2019-12-02-111027_RCM-YG1H4JGH8.crash Crash log diagnostic report codinganarchy (Matthew Tanous), 12/02/2019 04:21 PM

Related issues

Related to Ruby master - Bug #16239: Crash when accessing postgresql-12Third Party's IssueActions
Actions #1

Updated by jeremyevans0 (Jeremy Evans) about 2 years ago

  • Related to Bug #16239: Crash when accessing postgresql-12 added

Updated by jeremyevans0 (Jeremy Evans) about 2 years ago

  • Status changed from Open to Third Party's Issue

This crash happens inside the pg gem. It's either caused by the pg gem, libpq (PostgreSQL), or one of the internal Mac OS libraries listed.

/usr/lib/system/libsystem_platform.dylib(_sigtramp+0x1d) [0x7fff6e865b1d]
/usr/lib/system/libdispatch.dylib(_dispatch_mgr_queue_push+0x29) [0x7fff6e61e44e]
/usr/lib/system/libdispatch.dylib(0x7fff6e61450e) [0x7fff6e61450e]
/usr/lib/system/libdispatch.dylib(0x7fff6e620567) [0x7fff6e620567]
/System/Library/Frameworks/Security.framework/Versions/A/Security(_ZN8Security12KeychainCore14StorageManager14tickleKeychainEPNS0_12KeychainImplE+0x1e5) [0x7fff439ee661]
/System/Library/Frameworks/Security.framework/Versions/A/Security(0x7fff437c1374) [0x7fff437c1374]
/System/Library/Frameworks/Security.framework/Versions/A/Security(0x7fff439906a1) [0x7fff439906a1]
/System/Library/Frameworks/Security.framework/Versions/A/Security(0x7fff439b51ef) [0x7fff439b51ef]
/System/Library/Frameworks/Security.framework/Versions/A/Security(0x7fff439c0504) [0x7fff439c0504]
/System/Library/Frameworks/Security.framework/Versions/A/Security(0x7fff439c3d50) [0x7fff439c3d50]
/System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal(keychain_query+0x213) [0x7fff5928af43]
/System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal(hx509_certs_find+0x5c) [0x7fff59288b8c]
/System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal(_krb5_pk_find_cert+0x1d2) [0x7fff59247592]
/System/Library/Frameworks/GSS.framework/Versions/A/GSS(_gsspku2u_acquire_cred+0x26b) [0x7fff39c6498b]
/System/Library/Frameworks/GSS.framework/Versions/A/GSS(gss_acquire_cred+0x3ac) [0x7fff39c49bbc]
/usr/local/opt/postgresql/lib/libpq.5.dylib(pg_GSS_have_cred_cache+0x36) [0x108e6e6e3]
/usr/local/opt/postgresql/lib/libpq.5.dylib(0x108e5ceb0) [0x108e5ceb0]
/usr/local/opt/postgresql/lib/libpq.5.dylib(0x108e5a026) [0x108e5a026]
/usr/local/opt/postgresql/lib/libpq.5.dylib(0x108e5a1ad) [0x108e5a1ad]
/Users/mtanous/.rvm/gems/ruby-2.6.4/gems/pg-1.1.4/lib/pg_ext.bundle(gvl_PQconnectdb_skeleton+0x11) [0x108e1ab21]
/Users/mtanous/.rvm/rubies/ruby-2.6.4/lib/libruby.2.6.dylib(call_without_gvl+0xb9) [0x10537a6b9]
/Users/mtanous/.rvm/gems/ruby-2.6.4/gems/pg-1.1.4/lib/pg_ext.bundle(gvl_PQconnectdb+0x2d) [0x108e1aafd]
/Users/mtanous/.rvm/gems/ruby-2.6.4/gems/pg-1.1.4/lib/pg_ext.bundle(pgconn_init+0x79) [0x108e1fc59]
/Users/mtanous/.rvm/rubies/ruby-2.6.4/lib/libruby.2.6.dylib(vm_call0_body+0x276) [0x1053bb8d6]

It's very similar to #16239. If I had to guess, this is a PostgreSQL issue with GSS authentication on Mac OS. Please try contacting the PostgreSQL developers.

Actions

Also available in: Atom PDF