[ https://issues.apache.org/jira/browse/LOGCXX-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thorsten Schöning resolved LOGCXX-458. -------------------------------------- Resolution: Duplicate Im closing this in favour of LOGCXX-485, because this hasn't been reported anymore for the old release and with the approach in LOGCXX-485 this should be fixed once and for all. > Does log4cxx::Level::getError() leak memory? > -------------------------------------------- > > Key: LOGCXX-458 > URL: https://issues.apache.org/jira/browse/LOGCXX-458 > Project: Log4cxx > Issue Type: Bug > Affects Versions: 0.10.0 > Reporter: Michael Herzlich > > Hi there, > I have posted a question about the possible memory leak at stackoverflow: > http://stackoverflow.com/questions/33546286/does-log4cxxlevelgeterror-leak-memory?noredirect=1#comment54872303_33546286 > Could anybody verify this? Is this behavior by intention? -- This message was sent by Atlassian JIRA (v6.3.4#6332)