WIP: ENH: avoid potential HashPtrTable memory leaks (#1286) (!256) · Merge requests · Development / openfoam · GitLab

GitLab now enforces expiry dates on tokens that originally had no set expiration date. Those tokens were given an expiration date of one year later. Please review your personal access tokens, project access tokens, and group access tokens to ensure you are aware of upcoming expirations. Administrators of GitLab can find more information on how to identify and mitigate interruption in our documentation.

Mark OLESEN requested to merge feature-HashPtrTable into develop May 03, 2019

in previous versions the HashPtrTable used a HashTable<T*> for its underlying storage and added additional routines for deallocating memory when items were deleted or the table was cleared.

This generally works well, but direct use of any HashTable<T*> removal methods without additional wrapping results in memory leaks.

The safer means is to use a container with its own memory management. For example, HashTable<autoPtr>.

Any memory cleanup now becomes automatic.