Changes between Version 4 and Version 5 of Commentary/Rts/Storage/CAFs


Ignore:
Timestamp:
Oct 6, 2009 11:32:09 PM (5 years ago)
Author:
diatchki
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Commentary/Rts/Storage/CAFs

    v4 v5  
    88To 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.   
    99 
    10 To achieve this, during GC we maintain a linked list of static objects that are still live. 
     10To achieve this, all static objects are linked together with the static link field.  During GC we maintain traverse the static objects to see which are still live. 
    1111Closures that might refer to CAFs contain a Static Reference Table (SRT) which indicates what 
    12 CAFs are still in use by the closure. 
     12static objects are still needed.