[JBoss JIRA] Updated: (NETTY-310) Memory leak in netty-3.2.0.BETA1.jar

Sat May 1 23:13:06 EDT 2010

     [ https://jira.jboss.org/jira/browse/NETTY-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benoit Sigoure updated NETTY-310:
---------------------------------

    Attachment: 3.2-gc-log.txt

Output with full GC log when run against 3.2.0.BETA1 (leak).

> Memory leak in netty-3.2.0.BETA1.jar
> ------------------------------------
>
>                 Key: NETTY-310
>                 URL: https://jira.jboss.org/jira/browse/NETTY-310
>             Project: Netty
>          Issue Type: Bug
>    Affects Versions: 3.2.0.BETA1
>         Environment: $ uname -a
> Darwin hactar.local 10.3.0 Darwin Kernel Version 10.3.0: Fri Feb 26 11:58:09 PST 2010; root:xnu-1504.3.12~1/RELEASE_I386 i386
> $ javac -version
> javac 1.6.0_17
> $ java -version
> java version "1.6.0_17"
> Java(TM) SE Runtime Environment (build 1.6.0_17-b04-248-10M3025)
> Java HotSpot(TM) 64-Bit Server VM (build 14.3-b01-101, mixed mode)
>            Reporter: Benoit Sigoure
>            Assignee: Trustin Lee
>            Priority: Blocker
>         Attachments: 3.1-gc-log.txt, 3.2-gc-log.txt, TestServer.java
>
>
> I'm currently writing an application against 3.2.0.BETA1 that kept dying with {{OutOfMemoryError}}.  The heap contained a very large number of objects owned by Netty ({{DefaultChannelFuture}}, {{LinkedTransferQueue$Node}}, {{DownstreamMessageEvent}}, {{BigEndianHeapChannelBuffer}}).  After being puzzled for a while, I backported it against 3.1.5.GA and the leak disappeared.  I couldn't reproduce the problem so instead I trimed down my code as much as I could and ended up with 110 lines in 4 classes, using no external dependencies other than Netty and the JDK.  When compiled and run against 3.1.5.GA, the heap size remains mostly constant.  When compiled and run against 3.2.0.BETA1, the heap keeps growing until the JVM is struggling, doing full GCs all the time.
> I'm going to attach the code and GC log to this issue.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira