diff options
| author | shyouhei <shyouhei@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2010-12-03 03:58:54 +0000 |
|---|---|---|
| committer | shyouhei <shyouhei@b2dd03c8-39d4-4d8f-98ff-823fe69b080e> | 2010-12-03 03:58:54 +0000 |
| commit | e18e1314a969ae8ad81a0f83f0100d0a6eeb888e (patch) | |
| tree | 577d8ea7362e7abfd321e5c681132a04935ea96e /ChangeLog | |
| parent | eb702efcfafa63c3a13920db1cb00338007d4708 (diff) | |
| download | ruby-e18e1314a969ae8ad81a0f83f0100d0a6eeb888e.tar.gz | |
* ChangeLog: oops, typo.
git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@30067 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Diffstat (limited to 'ChangeLog')
| -rw-r--r-- | ChangeLog | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -7,7 +7,7 @@ Fri Dec 3 12:41:52 2010 URABE Shyouhei <shyouhei@ruby-lang.org> * 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 + space is about to be freed. Those objects, if any, remains 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. |