From: jessebs@... Date: 2019-02-01T20:56:21+00:00 Subject: [ruby-core:91379] [Ruby trunk Bug#15490] socket.rb - recurring segmentation faults Issue #15490 has been updated by jessebs (Jesse Bowes). I have run into a similar issue using Ruby 2.5.1 but unfortunately don't have an easy way to reproduce. A couple of things that help mitigate it (and may be useful for finding the actual issue): getaddrinfo is in the backtrace and this is happening around some network code for me. I found that using an IP address instead of hostname makes the issue go away. Another option that I have found is that around the code giving problems, turning off Garbage Collection will make it go away as well (GC.disable). ---------------------------------------- Bug #15490: socket.rb - recurring segmentation faults https://bugs.ruby-lang.org/issues/15490#change-76634 * Author: matthew.oriordan (Matthew O'Riordan) * Status: Open * Priority: Normal * Assignee: * Target version: * ruby -v: ruby 2.6.0p0 (2018-12-25 revision 66547) [x86_64-darwin18] * Backport: 2.4: UNKNOWN, 2.5: UNKNOWN, 2.6: UNKNOWN ---------------------------------------- With Ruby 2.5.3p105 and now with Ruby 2.6.0 following our recent upgrade, we are sadly still seeing reasonably frequent segmentation faults from Ruby, specifically within socket.rb Looking in socket.rb, it seems it's related to the address lookup: Addrinfo.getaddrinfo(nodename, service, family, socktype, protocol, flags).each(&block) Segfault report below in full. Attached are diagnostic reports too. If there is anything I can do to help reproduce I will, however sadly I have never been able to reproduce reliably, yet sadly it happens once every few days. ---Files-------------------------------- ruby_2018-12-31-032126-2_MacBook-Pro.crash (46.8 KB) ruby_2018-12-31-032126-3_MacBook-Pro.crash (46.8 KB) ruby_2018-12-31-032126-1_MacBook-Pro.crash (46.8 KB) ruby_2018-12-31-032125_MacBook-Pro.crash (46.8 KB) bug-15490.log (833 KB) -- https://bugs.ruby-lang.org/ Unsubscribe: