From: Andrew Selder Date: 2018-11-15T09:28:48-08:00 Subject: [ruby-core:89820] Ruby 2.5.x SegFaulting on OS X in GC Hi all, We recently upgraded to Ruby 2.5.3 and our developers started seeing SegFaults in random place when working with our app. There doesn���t seem to be any pattern to where it happens at our application level, but all of the C level backtraces point back to the same place. -- C level backtrace information ------------------------------------------- 0 libruby.2.5.dylib 0x0000000105542f37 rb_vm_bugreport + 135 1 libruby.2.5.dylib 0x00000001053b8bd3 rb_bug_context + 467 2 libruby.2.5.dylib 0x00000001054b0ee1 sigsegv + 81 3 libsystem_platform.dylib 0x00007fff62dbab3d _sigtramp + 29 4 libruby.2.5.dylib 0x00000001053d2f63 rb_gc_mark_machine_stack + 99 5 libruby.2.5.dylib 0x0000000105531449 rb_execution_context_mark + 137 6 libruby.2.5.dylib 0x000000010539f50b cont_mark + 27 7 libruby.2.5.dylib 0x00000001053de49e gc_marks_rest + 94 8 libruby.2.5.dylib 0x00000001053dcb60 gc_start + 2880 All of the crashes have been at rb_gc_mark_machine_stack + 99 I���ve filed a bug at ruby-lang.org (https://bugs.ruby-lang.org/issues/15308). It looks like there have been many other similar reports, all of the having that rb_gc_mark_machine_stack + 99 in common https://bugs.ruby-lang.org/issues/14714 https://bugs.ruby-lang.org/issues/14334 Has there been any progress on resolving this issue? I realize that Ruby is an open source volunteer project, but having the current version of Ruby segfaulting consistently on a major operating system seems like a big deal. I would hate to be stuck on Ruby 2.4 forever. Thanks, Andrew Selder Unsubscribe: