Noticed recently that setting loc to null (and assuming we've cleared all other references) will allow some atoms to linger indefinitely because walk_to is still executing on the atom in the scheduler so it can't be garbage collected...
I suppose its not a big issue, but it might not be clear, especially to new developers, that walk(src, 0) should be called when setting loc to null if walk_to is ever used with that atom.
ID:1270999
![]() May 23 2013, 4:47 am
|
|||||||
| |||||||