Memory leak in ZlibEncoder/Decoder?

[Norman Maurer]

Well it should get freed as you have a new ZlibEncoder instance in a
new ChannelPipeline. The Old ChannelPipeline and the ZlibEncoder
should get picked up by the GarbageCollector then.

Bye,
Norman

Ps: You may want to hop in #netty irc channel (irc.freenode.org) so we
can talk about it in realtime

2011/10/18 Evil Ipos <evil.ipos at gmail.com>:
> When you look at byte[] classes you see that it's growing over time. Most
> byte[] usage come from ZlibEncoder/window, pending_buf.
>
> I think when client disconnect this buffer should be freed.
>
> --
> View this message in context: http://netty-forums-and-mailing-lists.685743.n2.nabble.com/Memory-leak-in-ZlibEncoder-Decoder-tp6901578p6903860.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
>