Issue #9761 has been updated by Nobuyoshi Nakada.

Status changed from Open to Feedback

Seems `objspace_malloc_increase()` already runs GC after `xmalloc` and `xcalloc` if `ruby_gc_stress` is set.
You may want it to run after `xrealloc` too?
Or to run full marking?

----------------------------------------
Feature #9761: TRY_WITH_GC with ruby_gc_stress
https://bugs.ruby-lang.org/issues/9761#change-46269

* Author: _ wanabe
* Status: Feedback
* Priority: Normal
* Assignee: 
* Category: core
* Target version: 
----------------------------------------
I hope `TRY_WITH_GC()` may use `ruby_gc_stress` value.

Currently, `ruby_gc_stress` doesn't affect simple `xmalloc()`/`xrealloc()`/`xcalloc()`.
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 `BigDecimal_new()`.

---Files--------------------------------
try_with_gc-with-gc_stress.patch (691 Bytes)


-- 
https://bugs.ruby-lang.org/