Memory Leak

[huican ping]

1:) Plaese don't create timer for each pipeline object, you can create
one, and all pipeline objects refer it.
2:) make sure you call timer.stop() when it is not used anymore.

On Mon, Mar 15, 2010 at 11:18 AM, ajay_bhosle <ajay.bhosle at zapak.co.in> wrote:
>
> Hi,
>
>   I am running out of memory which i believe is caused due to
> HashedWheelTimer being used in ReadTimeOutHandler, below is the snapshot of
> the heap memory which keeps on increasing. Has anyone come across this
> issue, please let me know.
>
>   1:        727040       40714240
> [Lorg.jboss.netty.util.internal.ConcurrentIdentityHashMap$HashEntry;
>   2:        727849       34936752
> java.util.concurrent.locks.ReentrantLock$NonfairSync
>   3:        727040       34897920
> org.jboss.netty.util.internal.ConcurrentIdentityHashMap$Segment
>   4:        181760       13086720
> org.jboss.netty.util.internal.ConcurrentIdentityHashMap
>   5:        181760       13086720
> org.jboss.netty.util.internal.ConcurrentIdentityHashMap$KeyIterator
>   6:        181760       10178560
> [Lorg.jboss.netty.util.internal.ConcurrentIdentityHashMap$Segment;
>   7:        181760        4362240
> org.jboss.netty.util.internal.ConcurrentIdentityHashMap$KeySet
>
> Thanks
> Ajay
> --
> View this message in context: http://n2.nabble.com/Memory-Leak-tp4738033p4738033.html
> Sent from the Netty User Group mailing list archive at Nabble.com.
> _______________________________________________
> netty-users mailing list
> netty-users at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/netty-users
>