[Dune] [#556] GenericReferenceElements leak memory

[Dune]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#556 - GenericReferenceElements leak memory
User who did this - Martin Nolte (nolte)

----------
I think this is a singleton-problem. The singleton GenericReferenceElement internally uses the singleton SmallObjectPool. Now, gcc creates the singletons the the order I stated. Hence, the singletons are deleted in the inverse order. Therefore, SmallObjectPool cannot free up the memory that is still used by the GenericReferenceElement.

Everything would be fine, if SmallObjectPool were created before GenericReferenceElement. Then, the destruction would be the other way round.

Actually, this is not a real problem, though. The SmallObjectPool is designed to allocate memory on demand and only free it on program termination. It is annoying, though.
----------

More information can be found at the following URL:
http://www.dune-project.org/flyspray/index.php?do=details&task_id=556#comment946

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.