rb_gc() kicks gc_finalize_deferred(), which invokes finalizers.
This means that any Ruby program can be run this point and
it may be thread switching points and so on.
However, it is difficult to think it invokes any Ruby programs.
For example, GC.compact use rb_gc() to implement it, howver,
any Ruby program must not be run on this timing.
For this reason (it is difficult to image it run any Ruby program),
I removed gc_finalize_deferred() line in rb_gc().
This patch solves GC.compact issue.
[Bug #15809] and re-enable GC.compact test.
Related issues
Bug #15809: GC.verify_compaction_references - intermittent SEGV's on multiple platforms
Added by ko1 (Koichi Sasada) almost 5 years ago
Do not kick finalizers on rb_gc().
rb_gc() kicks gc_finalize_deferred(), which invokes finalizers.
This means that any Ruby program can be run this point and
it may be thread switching points and so on.
However, it is difficult to think it invokes any Ruby programs.
For example,
GC.compactuserb_gc()to implement it, howver,any Ruby program must not be run on this timing.
For this reason (it is difficult to image it run any Ruby program),
I removed
gc_finalize_deferred()line in rb_gc().This patch solves GC.compact issue.
[Bug #15809] and re-enable GC.compact test.