ruby-concurrency/concurrent-ruby

Version 1.2.2 crashes with Segmentation fault

ihopciklumer opened this issue · 3 comments

ihopciklumer commented 
* Operating system:                Mac Sonoma 14.2
* Ruby implementation:             Ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c)
* `concurrent-ruby` version:       1.2.2
* `concurrent-ruby-ext` installed:  no
* `concurrent-ruby-edge` used:     no

Previously used version 1.1.10 but after updating to 1.2.2 get Segmentation fault at 0x0000000027142620

eregon commented

We'll need more information than that:

  • the full output
  • the Crash Report log file under DiagnosticReports directory

You said

`concurrent-ruby-ext` installed:  no

in which case it cannot be a bug of concurrent-ruby, and should instead be reported (with as much information as possible to https://bugs.ruby-lang.org/)

ihopciklumer commented

concurrent-ruby-ext installation didn't help. Last 10 lines of output. @eregon Regarding diag file. Under Diagnostic directroy I have 100 files. What the name of the file or how determine where to look. I looked through some but no errros mentioned there

.rvm/gems/ruby-2.7.1@core5/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/atomic/mutex_atomic_fixnum.rb
.rvm/gems/ruby-2.7.1@core5/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/atomic/atomic_fixnum.rb
.rvm/gems/ruby-2.7.1@core5/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/atomic/cyclic_barrier.rb
.rvm/gems/ruby-2.7.1@core5/gems/concurrent-ruby-1.2.2/lib/concurrentruby/concurrent/atomic/mutex_count_down_latch.rb
.rvm/gems/ruby-2.7.1@core5/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/atomic/java_count_down_latch.rb
.rvm/gems/ruby-2.7.1@core5/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/atomic/count_down_latch.rb
.rvm/gems/ruby-2.7.1@core5/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/synchronization/lock.rb
.rvm/gems/ruby-2.7.1@core5/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/atomic/read_write_lock.rb
.rvm/rubies/ruby-2.7.1/lib/ruby/2.7.0/-darwin20/fiber.bundle
.rvm/gems/ruby-2.7.1@core5/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/atomic/locals.rb
.rvm/gems/ruby-2.7.1@core5/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/atomic/fiber_local_var.rb
.rvm/gems/ruby-2.7.1@core5/gems/concurrent-ruby-1.2.2/lib/concurrent-ruby/concurrent/atomic/thread_local_var.rb

bensheldon commented

To add a little more details why we're unable to help :-(

  • if you're only using the Ruby version (not the c-ext) of Concurrent Ruby, any segmentation fault (e.g. the Ruby VM crashing) would be the responsibility of the Ruby VM.
  • you're using Ruby 2.7.1, and the 2.7.x release is EOL (March, 2023), and the most recent patch which is Ruby 2.7.8 (so it's possible the segfault has been fixed in later patched versions of Ruby 2.7.x)
  • 👍1