Issue #15490 has been updated by matthew.oriordan (Matthew O'Riordan).


Some background to how I have worked around this for now, which may be useful.
I use the parallel gem https://github.com/grosser/parallel, which can parallelise tasks using threads of processes.  When switching from processes to threads, this issue has gone away.  In some code baths with a CLI we use locally, processes are preferable given the isolation from the running code, however in this case it was not an issue to use threads and arguably also better from a resource perspective.

----------------------------------------
Bug #15490: socket.rb - recurring segmentation faults
https://bugs.ruby-lang.org/issues/15490#change-77933

* Author: matthew.oriordan (Matthew O'Riordan)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: ruby 2.6.3p62 (2019-04-16 revision 67580) [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: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>