From: Mathieu Bouchard Date: 2000-10-16T14:41:06+09:00 Subject: [ruby-talk:5563] Re: GC: malloc_memories > |precipitate a new GC cycle if lots of resizing is done. My biggest > |concern, though, is that the GC operates on object cells, which are not > |allocated with ruby_x*alloc procedures, but the malloc_memories system > malloc_memories is to retrieve additional, inexact information about > memory usage. If we have more accurate information, feel free to > advise me. ok, malloc_memories is going to the trashcan. I'll put a counter that's incremented in rb_newobj() and reset in rb_gc(). this should separate completely two parts (?): * newobj/gc * malloc/free matju