Open pixelzoom opened 4 years ago
The above commits add a comment for each Property.link
, DerivedProperty
or Multilink
explaining why they don't need to be disposed/unlinked.
In our case, most of the objects are created at the start of the simulation and are not meant to be disposed. There is only one place where a new VStrut
needs to be created sometimes, and the old one was not disposed until bd6e9a6.
... most of the objects are created at the start of the simulation and are not meant to be disposed. There is only one place where a new VStrut needs to be created sometimes ...
When you get to #8... This is the type of information that we typically put in implementation-notes.md, under a "Memory Management" heading.
Related to #2 (code review), there are 3 items related to memory management:
There are zero definitions of
dispose
in sim-specific code, and zero calls todispose
of common-code. That may be OK, or it may point to memory leaks.Things to do:
link
), have an associated cleanup call (eg.unlink
) or document why one is not needed.