[jira] [Commented] (LOG4J2-2362) ReusableObjectMessage retains object reference after use

["ASF GitHub Bot (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/LOG4J2-2362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16528169#comment-16528169 ] 

ASF GitHub Bot commented on LOG4J2-2362:
----------------------------------------

GitHub user cakofony opened a pull request:

    https://github.com/apache/logging-log4j2/pull/185

    LOG4J2-2362 ReusableObjectMessage memory leak

    ReusableObjectMessage would previously retain a reference to
    the most recently logged object.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/cakofony/logging-log4j2 LOG4J2-2362

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/logging-log4j2/pull/185.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #185
    
----
commit bb5594987ef85a360f1c7d9473b232ea6e4451a8
Author: Carter Kozak <ck...@...>
Date:   2018-06-29T20:02:55Z

    LOG4J2-2362 ReusableObjectMessage memory leak
    
    ReusableObjectMessage would previously retain a reference to
    the most recently logged object.

----


> ReusableObjectMessage retains object reference after use
> --------------------------------------------------------
>
>                 Key: LOG4J2-2362
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2362
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.11.0
>            Reporter: Carter Kozak
>            Priority: Major
>
> ReusableParameterizedMessage is not affected because "swapParameters" hands off parameter references to a reusable event which is reset after usage.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)