Regent: automatically destroy ispaces, fspaces, regions, partitions #813
Labels
best effort
indicates the milestone tag for an issue is a goal rather than a commitment
enhancement
planned
Feature/fix to be actively worked on - needs release target
Regent
Issues pertaining to Regent
Milestone
Currently Regent leaks ispaces, fspaces, regions and partitions if they are not manually destroyed with
__delete
. If an application creates any of these dynamically, this turns into a O(N) leak in the length of the run. Ideally Regent should destroy any resources that it creates.In order to do this correctly, we'll need to do an escape analysis on any objects being returned. As a conservative approximation, anything being packed in an fspace, or anything being directly returned, should be considered to escape. For the moment it's probably ok to let those leak (if the user does not explicitly
__delete
) since this is an uncommon case.I have a partial (buggy) solution in branch
fix-regent-memory-leaks
. At the moment it suffers from double deletions due to #812.Probably not a direct cause of #711, but worth keeping in mind for that issue.
The text was updated successfully, but these errors were encountered: