TRY_WITH_GC with ruby_gc_stress
TRY_WITH_GC() may use
ruby_gc_stress doesn't affect simple
It is usefull to make these functions under gc-stress.
For example, #9657 is difficult to reproduce on trunk because there is not object creation but memory allocation after
#3 [ruby-core:62106] Updated by wanabe (_ wanabe) almost 3 years ago
- File try_with_gc-with-gc_stress.patch View added
- Category deleted (
- Status changed from Feedback to Open
I have written but I have not been able to avoid both temporary assignment and duplication of garbage_collect_with_gvl().
#6 [ruby-core:62118] Updated by wanabe (_ wanabe) almost 3 years ago
Nobuyoshi Nakada wrote:
objspace_malloc_increase()already runs GC after
You may want it to run after
Or to run full marking?
Sorry for my poor code reading...
It is enough to add a case of
xrealloc for my concern, reproducing #9657.
Anyone can close/reject this ticket if you think this is far from the original proposal.
#7 [ruby-core:62122] Updated by nobu (Nobuyoshi Nakada) almost 3 years ago
- Status changed from Open to Closed
- % Done changed from 0 to 100