Bug #14678
closedSegmentation fault in pg
Added by ttanimichi (Tsukuru Tanimichi) over 7 years ago. Updated about 6 years ago.
Description
This error don't reproduce in Ruby 2.5.0 but reproduce in 2.5.1
$ bundle ex rspec
/Users/tanimichi.tsukuru/ghq/github.com/moneyforward/moneyplus/vendor/bundle/ruby/2.5.0/gems/pg-0.21.0/lib/pg.rb:56: [BUG] Segmentation fault at 0x0000000000000000
(snip)
Abort trap: 6
Files
| ruby_2018-04-11-182206_mf-C0037-mm01.crash (37.1 KB) ruby_2018-04-11-182206_mf-C0037-mm01.crash | ttanimichi (Tsukuru Tanimichi), 04/11/2018 10:13 AM | ||
| bug-14678.log (319 KB) bug-14678.log | nobu (Nobuyoshi Nakada), 04/11/2018 12:47 PM | ||
| ruby_2018-05-09-135249_iains-MacBook-Air.crash (25.7 KB) ruby_2018-05-09-135249_iains-MacBook-Air.crash | yb601 (Iain Barnett), 05/09/2018 12:58 PM | ||
| rails_2018-8-13.crash (13.2 KB) rails_2018-8-13.crash | crash log | Ricochet (SeHoon Park), 08/14/2018 05:48 PM |
Updated by nobu (Nobuyoshi Nakada) over 7 years ago
Actions
#1
[ruby-core:86508]
- File bug-14678.log bug-14678.log added
- Description updated (diff)
- Status changed from Open to Feedback
Could you show small code to reproduce it and/or show local variables with a debugger?
Updated by yb601 (Iain Barnett) over 7 years ago
Actions
#2
[ruby-core:86955]
- File ruby_2018-05-09-135249_iains-MacBook-Air.crash ruby_2018-05-09-135249_iains-MacBook-Air.crash added
Hi,
I have the same problem, exactly the same Ruby version and revision. I can supply a crash report or 3 if you require, here is some code that causes it:
require 'nenv'
require 'dotenv/load'
require 'sequel'
require 'pry-byebug'
unless defined? DB
DB = Sequel.connect(Nenv.database_url) # <-- this line
end
ruby/2.5.0/gems/sequel-5.8.0/lib/sequel/adapters/postgres.rb:146: [BUG] Segmentation fault at 0x0000000000000000
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin13]
I was running ruby 2.5.0p0 (2017-12-25 revision 61468) [x86_64-darwin13] with the same code, no problems.
Let me know if you need any more.
Regards,
iain
Updated by Ricochet (SeHoon Park) about 7 years ago
Actions
#3
[ruby-core:88485]
- File rails_2018-8-13.crash rails_2018-8-13.crash added
I wanted to use ruby v2.5.1 instead v2.5.0
But I got this error.
With ruby v2.5.0, my rails project works great without any error.
I was using Rails v5.2.1 on macbook pro macos High Sierra 10.13.6 with Postgres.app v2.1.4
Updated by masutaka (Takashi Masuda) about 7 years ago
Actions
#4
[ruby-core:89524]
I avoided this problem by reinstalling vendor/bundle. My OS is macOS High Sierra.
I guess vendor/bundle/ruby/2.5.0/gems/pg-0.21.0/lib/pg_ext.bundle is inconsistent.
After I overwrote with the pg_ext.bundle made in ruby-2.5.0, it reproduced.
Updated by masutaka (Takashi Masuda) about 7 years ago
Actions
#5
[ruby-core:89525]
- ruby -v changed from ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin16] to ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-darwin17]
Updated by masutaka (Takashi Masuda) about 7 years ago
Actions
#6
- ruby -v changed from ruby 2.5.3p105 (2018-10-18 revision 65156) [x86_64-darwin17] to ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-darwin16]
Updated by nobu (Nobuyoshi Nakada) about 7 years ago
Actions
#7
[ruby-core:89535]
masutaka (Takashi Masuda) wrote:
I avoided this problem by reinstalling vendor/bundle. My OS is macOS High Sierra.
I guess vendor/bundle/ruby/2.5.0/gems/pg-0.21.0/lib/pg_ext.bundle is inconsistent.
After I overwrote with the pg_ext.bundle made in ruby-2.5.0, it reproduced.
Do you mean they are binary incompatible?
Only the difference between 2.5.0 and 2.5.1 in the headers seems [Bug #14425].
Updated by masutaka (Takashi Masuda) about 7 years ago
Actions
#8
[ruby-core:89608]
Yes. I'm not sure but they are binary incompatible.
Updated by jeremyevans0 (Jeremy Evans) about 6 years ago
Actions
#9
- Status changed from Feedback to Closed