You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the major sources for memory leaks in Parcels is the lack of destructors (__del__(self)) functions, which are called when an object is deleted. This accounts mostly for dynamic member variable data (e.g. Numpy/xarray/dask matrices) that are initialised in the constructor, expanded during execution and so on. But, for the removal, Parcels currently relies on the interpreter finding all the references. That is prone to error, and a class that does not use its member array data should release them.
One of the major sources for memory leaks in Parcels is the lack of destructors (
__del__(self)
) functions, which are called when an object is deleted. This accounts mostly for dynamic member variable data (e.g. Numpy/xarray/dask matrices) that are initialised in the constructor, expanded during execution and so on. But, for the removal, Parcels currently relies on the interpreter finding all the references. That is prone to error, and a class that does not use its member array data should release them.Thanks to @CKehl for bringing this up
The text was updated successfully, but these errors were encountered: