The subject matter expert in that affected code has been swamped with work, so I'd imagine that's why it hasn't been looked at yet. If you could provide a patch, that should help us get this moving forward, though.
On 14 April 2017 at 02:17, Adrien Grand <[email protected]> wrote: > Hello, > > While reviewing a heap dump a couple weeks ago, I found that log4j was > using more memory than I would expect, and this turned out to come from a > static ThreadLocal in ParameterizedMessage. Could someone look at the > following issue? > https://issues.apache.org/jira/browse/LOG4J2-1858 > > Thanks. > > Adrien > -- Matt Sicker <[email protected]>
