[#62297] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap. — Eric Wong <normalperson@...>
nari@ruby-lang.org wrote:
7 messages
2014/05/02
[#62307] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap.
— SASADA Koichi <ko1@...>
2014/05/03
(2014/05/03 4:41), Eric Wong wrote:
[#62402] Re: [ruby-cvs:52906] nari:r45760 (trunk): * gc.c (gc_after_sweep): suppress unnecessary expanding heap.
— Eric Wong <normalperson@...>
2014/05/05
SASADA Koichi <ko1@atdot.net> wrote:
[#62523] [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan — ko1@...
Issue #9632 has been updated by Koichi Sasada.
3 messages
2014/05/11
[#62556] doxygen (Re: Re: [ruby-trunk - Feature #9632] [PATCH 0/2] speedup IO#close with linked-list from ccan) — Tanaka Akira <akr@...>
2014-05-11 8:50 GMT+09:00 Eric Wong <normalperson@yhbt.net>:
3 messages
2014/05/13
[#62727] [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl — Eric Wong <normalperson@...>
rb_unlink_method_entry may cause old_me to be swept before the new
7 messages
2014/05/24
[#63039] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— SASADA Koichi <ko1@...>
2014/06/10
Hi,
[#63077] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— Eric Wong <normalperson@...>
2014/06/10
SASADA Koichi <ko1@atdot.net> wrote:
[#63086] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— SASADA Koichi <ko1@...>
2014/06/11
(2014/06/11 4:47), Eric Wong wrote:
[#63087] Re: [RFC] vm_method.c (rb_method_entry_make): avoid freed me in m_tbl
— Eric Wong <normalperson@...>
2014/06/11
SASADA Koichi <ko1@atdot.net> wrote:
[#62862] [RFC] README.EXT: document rb_gc_register_mark_object — Eric Wong <normalperson@...>
Any comment on officially supporting this as part of the C API?
5 messages
2014/05/30
[ruby-core:62720] [ruby-trunk - Feature #9761] TRY_WITH_GC with ruby_gc_stress
From:
nobu@...
Date:
2014-05-24 03:52:33 UTC
List:
ruby-core #62720
Issue #9761 has been updated by Nobuyoshi Nakada. Related to Bug #9859: An object with 6 instance variables causes SEGV added ---------------------------------------- Feature #9761: TRY_WITH_GC with ruby_gc_stress https://bugs.ruby-lang.org/issues/9761#change-46844 * Author: _ wanabe * Status: Closed * 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) xrealloc-with-gc_stress.patch (456 Bytes) -- https://bugs.ruby-lang.org/