Changes between Version 4 and Version 5 of Commentary/Rts/Storage/CAFs
- Oct 6, 2009 11:32:09 PM (4 years ago)
v4 v5 8 8 To avoid memory leaks caused by CAFs we need to detect when all values/functions that could potentially refer to a CAF are gone, and so it is safe to deallocate the CAF. 9 9 10 To achieve this, during GC we maintain a linked list of static objects thatare still live. 10 To achieve this, are still live. 11 11 Closures that might refer to CAFs contain a Static Reference Table (SRT) which indicates what 12 CAFs are still in use by the closure. 12 .