diff options
author | shyouhei <shyouhei@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2010-12-03 03:53:21 +0000 |
---|---|---|
committer | shyouhei <shyouhei@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2010-12-03 03:53:21 +0000 |
commit | 9d3ba342c90aeec8cec3011967b31bd1d03ae86b (patch) | |
tree | b481386e2aa9f7560c7ccc4f8bacd963692046b4 /gc.c | |
parent | adc978adc3932e5fdeb0bdc0622d2f52bf846dba (diff) | |
download | ruby-9d3ba342c90aeec8cec3011967b31bd1d03ae86b.tar.gz |
* gc.c (rb_objspace_free): With our "lazy-sweep" GC engine, it is
possible for an object to survive until its surrounding object
space is about to be freed. Those objects, if any, remains not
leaked for the rest of a process life. This is problematic
because for instance a T_DATA object may have its own destructor
to terminate something.
* vm.c (ruby_vm_destruct): ruby_current_vm termination should be
somewhere after rb_objspace_free for above reason.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30065 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'gc.c')
-rw-r--r-- | gc.c | 6 |
1 files changed, 6 insertions, 0 deletions
@@ -400,9 +400,15 @@ rb_objspace_alloc(void) return objspace; } +static void gc_sweep(rb_objspace_t *); +static void slot_sweep(rb_objspace_t *, struct heaps_slot *); +static void gc_clear_mark_on_sweep_slots(rb_objspace_t *); + void rb_objspace_free(rb_objspace_t *objspace) { + gc_clear_mark_on_sweep_slots(objspace); + gc_sweep(objspace); if (objspace->profile.record) { free(objspace->profile.record); objspace->profile.record = 0; |