You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by "Remko Popma (JIRA)" <ji...@apache.org> on 2016/05/17 07:54:12 UTC
[jira] [Commented] (LOG4J2-1387) Memory leak related to shutdown
hook
[ https://issues.apache.org/jira/browse/LOG4J2-1387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15286190#comment-15286190 ]
Remko Popma commented on LOG4J2-1387:
-------------------------------------
Any more information to address the memory leak is welcome. I have not done much analysis on this yet. If you can provide a patch that would be ideal but additional analysis on what the problem is would be useful too.
> Memory leak related to shutdown hook
> ------------------------------------
>
> Key: LOG4J2-1387
> URL: https://issues.apache.org/jira/browse/LOG4J2-1387
> Project: Log4j 2
> Issue Type: Bug
> Components: Core
> Affects Versions: 2.5
> Reporter: Yang ZHONG
>
> [~yang_zhong] reported this issue with the shutdown hook on LOG4J2-868 (cannot raise a new issue because this is disabled to defend against an Denial of Service attack):
> {quote}
> It's leaking memory in log4J 2.5 (AsyncLoggerContext) @ JDK 8u92.
> Total 2G memory used by 2 AsyncLoggerContext, each references 1G DefaultShutdownCallBackRegistry$1
> which references 4G DefaultShutdownCallBackRegistry
> which references 4G CopyOnWriteArrayList
> which references many many many DefaultShutdownCallBackRegistry$1
> How to turn it off or what's the work-around please?
> {quote}
> A workaround is to disable the shutdown hook in the configuration with
> {code}
> <Configuration status="WARN" shutdownHook="disable">
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org