Issue #17843 has been updated by alanwu (Alan Wu).


Apologies about my misleading statement about support for the OS.
It doesn't seem to be receiving security updates anymore so I had assumed it reached end of life.

Looking at the report, the crash happens after fork.
There was a Ruby crash in the [past](https://bugs.ruby-lang.org/issues/13646) that happens when calling `getaddrinfo()` in the fork child.
I sent Apple a bug report and they closed it as a duplicate, so I take it that they agree it's a bug in their system library. All they told me is that the bug I submitted is a duplicate with bug id 50511049 in their internal bug tracking system to which I have no access. They fixed the bug a few OS updates down the line.

Similar to this crash, that crash happens in `libdispatch`. Anecdotally, it seems that macOS's support for fork without exec isn't great, especially in older versions. I wouldn't be surprised if this is another system library problem.


A possible workaround for the crash might be running `bin/spring stop` and prefixing the `rails g` command with `DISABLE_SPRING=1 `. This should avoid forking the Ruby process.

In any case, I still recommend upgrading to a newer OS.

----------------------------------------
Bug #17843: Ruby on Rails error[BUG] Segmentation fault at 0x0000000000000110 ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x86_64-darwin15] (#42110)
https://bugs.ruby-lang.org/issues/17843#change-91787

* Author: nayaronfire (kk nayar)
* Status: Open
* Priority: Normal
* ruby -v: 3.0.1p64 
* Backport: 2.6: UNKNOWN, 2.7: UNKNOWN, 3.0: UNKNOWN
----------------------------------------
following tutorial

https://www.youtube.com/watch?v=nlKIJfv50U0

On this command
$ rails g scaffold Survey name:text laptop:binary os:text
the following error was generated with the following instruction

[BUG] Segmentation fault at 0x0000000000000110
ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x86_64-darwin15]
-- Crash Report log information --------------------------------------------
   See Crash Report log file under the one of following:                    
     * ~/Library/Logs/DiagnosticReports                                     
     * /Library/Logs/DiagnosticReports                                      
   for more details.                                                        
Don't forget to include the above Crash Report log file in bug reports. 
Expected behavior
should have created a scaffold with the above three fields which would facilitate migrating to db after this

Actual behavior
got the above error
ruby crash report_2021-04-30-194015.pdf

System configuration
Rails 6.1.3.1

ruby 3.0.1p64 (2021-04-05 revision 0fb782ee38) [x86_64-darwin15]

I am using OS X EL Capitan 10.11.6

I filed a bug in rails. They replied stating it is a ruby error

https://github.com/rails/rails/issues/42110

---Files--------------------------------
ruby crash report_2021-04-30-194015.pdf (48.8 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>