[LOG4J2-505] Memory leak with org.apache.logging.log4j.core.async.AsyncLoggerConfigHelper$Log4jEventWrapper

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Not A Problem
• Affects Version/s: 2.0-beta9
• Fix Version/s: 2.0-beta9
• Component/s: Core
• Assignee: Remko Popma
• Reporter: Tal Liron
• Created: 18/Jan/14 06:49
• Updated: 22/Feb/14 03:26
• Resolved: 18/Jan/14 12:49

Description

Instances of this class seem to be created but never garbage collected. Here is a jmap dump of the problem:

https://dl.dropboxusercontent.com/u/122806/jvm8_gc2.zip

Use jhat to analyze it: if you go to the instance count, you will see that the aforementioned class is way out of control.

Some background on how I discovered this, which may help: I am currently working with the Oracle OpenJDK team to debug a memory leak that has existed with JSR-292 (invokedynamic) that has been present since 7u40, and also plagues OpenJDK 8 right now. The bug is prevalent in the Nashorn engine, which is being shipped with JDK 8. Indeed, in the memory dump above, you'll see that JSR-292 and Nashorn classes are also out of control – but still second to the log4j class!