#41 Memory Leak in the class PropertyConfiguratorImpl

[Volker Wildi]

There is a memory leak in the current code.

I tested it with the version 1.1.

The according appender is not deleted by this class. If the overloaded pointer method is used the memory will be successfully freed. Otherwise not.

A possible fix is attached to this issue.

[Alexander Perepelkin]

Hello Volker,

Thank you for your care about the project.

Regarding the fix I should ask you whether you have any ideas in background why we would need to transfer ownership. There is even special comment in the code which warns about non-transferred ownership. If we change this behaviour, strange things might come up.
Consider the case when this appender is shared among several Categories. Then each of them will consider the appender as their own, and will probably try to delete it during their deconstruction effectively causing heap corruption.
Would you try your fix with the configuration when the same appender is shared actually please?