andreacavalli/netty5
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Fix a bug where the buffers are freed too early when a handler is removed or replaced

Browse Source
This commit is contained in:
Trustin Lee 2013-01-14 21:43:25 +09:00
parent a03bc6ea1d
commit e263769a55
1 changed files with 23 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

26
transport/src/main/java/io/netty/channel/DefaultChannelPipeline.java
View File

@ -598,9 +598,22 @@ final class DefaultChannelPipeline implements ChannelPipeline {
}
}
private void callAfterRemove(ChannelHandlerContext ctx) {
private void callAfterRemove(final ChannelHandlerContext ctx) {
final ChannelHandler handler = ctx.handler();
// Notify the complete removal.
try {
handler.afterRemove(ctx);
} catch (Throwable t) {
throw new ChannelPipelineException(
ctx.handler().getClass().getName() +
".afterRemove() has thrown an exception.", t);
}
// Free all buffers before completing removal.
ChannelHandler handler = ctx.handler();
ctx.executor().execute(new Runnable() {
@Override
public void run() {
if (handler instanceof ChannelInboundHandler) {
try {
((ChannelInboundHandler) handler).freeInboundBuffer(ctx);
@ -615,15 +628,8 @@ final class DefaultChannelPipeline implements ChannelPipeline {
notifyHandlerException(e);
}
}
// Notify the complete removal.
try {
handler.afterRemove(ctx);
} catch (Throwable t) {
throw new ChannelPipelineException(
ctx.handler().getClass().getName() +
".afterRemove() has thrown an exception.", t);
}
});
}
@Override