The GC module provides an interface to Ruby’s mark and sweep
garbage collection mechanism. Some of the underlying methods are also
available via the ObjectSpace module.
Disables garbage collection, returning true if garbage
collection was already disabled.
GC.disable #=> false GC.disable #=> true
VALUE
rb_gc_disable(void)
{
rb_objspace_t *objspace = &rb_objspace;
int old = dont_gc;
dont_gc = Qtrue;
return old;
}
Enables garbage collection, returning true if garbage
collection was previously disabled.
GC.disable #=> false GC.enable #=> true GC.enable #=> false
VALUE
rb_gc_enable(void)
{
rb_objspace_t *objspace = &rb_objspace;
int old = dont_gc;
dont_gc = Qfalse;
return old;
}
The allocated size by malloc().
It returns the allocated size by malloc().
static VALUE
gc_malloc_allocated_size(VALUE self)
{
return UINT2NUM((&rb_objspace)->malloc_params.allocated_size);
}
The number of allocated memory object by malloc().
It returns the number of allocated memory object by malloc().
static VALUE
gc_malloc_allocations(VALUE self)
{
return UINT2NUM((&rb_objspace)->malloc_params.allocations);
}
Initiates garbage collection, unless manually disabled.
VALUE
rb_gc_start(void)
{
rb_gc();
return Qnil;
}
returns current status of GC stress mode.
static VALUE
gc_stress_get(VALUE self)
{
rb_objspace_t *objspace = &rb_objspace;
return ruby_gc_stress ? Qtrue : Qfalse;
}
updates GC stress mode.
When ::stress = true, GC is invoked for all GC opportunity: all memory and object allocation.
Since it makes Ruby very slow, it is only for debugging.
static VALUE
gc_stress_set(VALUE self, VALUE bool)
{
rb_objspace_t *objspace = &rb_objspace;
rb_secure(2);
ruby_gc_stress = RTEST(bool);
return bool;
}
Commenting is here to help enhance the documentation. For example, code samples, or clarification of the documentation.
If you have questions about Ruby or the documentation, please post to one of the Ruby mailing lists. You will get better, faster, help that way.
If you wish to post a correction of the docs, please do so, but also file bug report so that it can be corrected for the next release. Thank you.
If you want to help improve the Ruby documentation, please see Improve the docs, or visit Documenting-ruby.org.