Attached is a patch that fixes this issue by replacing the troublesome usage of a VALUE to store the at_exit functions with a simple linked list. This patch was created against the ruby_2_3 branch. It should apply cleanly to most branche...evanphx (Evan Phoenix)
I'm hitting this as well, and looking over the code in question on 2.3.0, I wondering if the problem is that the at_exit pseudo-object is actually allocated within the body of rb_vm_t. It's address is taken and passed to `rb_ary_push`, w...evanphx (Evan Phoenix)
When entering an sclass, the context is tracked via the same cref mechanism used for class and module, specifically on the iseq->cref_stack. The bug is that the cref_stack is the wrong place to put the new cref because the scope is speci...evanphx (Evan Phoenix)
No, it shouldn't raise an exception. Process.daemon and fork both use after_fork() in C. That function should iterate all the threads and mark them as KILLED since they are all dead.
I have a worry about Koichi's approach. There are going to have to be places where (b) type Symbols are converted into (a) type Symbols. All those places will turn into DOS vectors. This is because SYMBOL_P() will have to detect both ty...evanphx (Evan Phoenix)
So sorry for the continual delay. I'm setting this up right now but it appears that I (evanphx on github) don't have access to push to ruby/ruby. When I am added, I can update the repo immediately.
evanphx (Evan Phoenix)04:21 PM Ruby Bug #12095: ruby_vm_at_exit can sometime cause a crash.