Use postponed jobs on Ruby 3.2.0 #196
Conversation
Otherwise it can cause a VM crash. Won't be a problem in 3.2.1.
| Can you elaborate on how this happens? As of 67ec8fe we should be forwarding to the thread which stackprof was started from, I'd think that would sidestep the issue (we know that thread has a stack because we ran code to start stackprof). |
| @jhawthorn I don't particularly understand the bug myself, all I know if that there is a race condition fixed by ruby/ruby#7116. I'm sure @tenderlove or @XrXr can actually explain the issue. |
| @jhawthorn I'm not 100% sure how it's happening. I agree it's odd since we should be forwarding the signal to only active and live threads, but the core files we recovered definitely showed the ec was not fully set up. Maybe there is a race condition when threads switch? Regardless of the root cause, I think we should merge this. At least it buys us time to figure out a stable repro. |
| @jhawthorn maybe the issue is in |
| Yes, I forgot to mention that the crash only happens in CPU mode. |
5 participants
Otherwise it can cause a VM crash.
Won't be a problem in 3.2.1.
cc @jhawthorn @tenderlove