objectRegistry can leak memory

As discussed with @Mattijs - since all HashTable operations are visible through objectRegistry, anything that removes entries using the HashTable methods can leak memory if the object is owned by the registry.

mentioned in commit 47493f50f1f03ce26a097624350bedfdf89d7edc

• checkOutByName() could be a rather convenient way to purge old, unwanted fields.

@andy - related to EP829 (will speak tomorrow)

odd-looking use of store() in basicThermo

mentioned in commit 1dea317a1059b50b8473cbb488174b97e78d3f2f

mentioned in commit 91bf628882c313032526fe3b5965d4501fc43ddb

Instead of checkOutByName() or equivalent, just corrected the handling of erase() to ensure that it doesn't leak memory. This provides the same functionality with an existing method name and plugs potential memory leaks.

mentioned in commit cb0a2636de46004feb26c419be0602c0520842be

mentioned in issue #613 (closed)

assuming resolved considering the commits above.

please open a new ticket if the issue persists.

closed