You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
voidmark() {
// We don't mark the objects, but we MUST mark the frames, otherwise they// can be garbage collected.// When we stop collection we will stringify the remaining frames, and then// clear them from the set, allowing them to be removed from out output.
stack_table->mark_frames();
rb_gc_mark(stack_table_value);
rb_gc_mark(tp_newobj);
rb_gc_mark(tp_freeobj);
}
It says it doesn't mark the objects, but we crash because while iterating over for (auto& obj: collector->object_list) { some objects are clearly garbage.
So I suspect we should mark them so they are pinned?
We started seeing crashes on our nightly CI since last friday night.
The first commit to fail was ruby/ruby@cb39283 (but could be a close parent).
I'll see if I can figure out what it is, but filing it here just in case.
The text was updated successfully, but these errors were encountered: