You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@james.apache.org by GitBox <gi...@apache.org> on 2022/03/04 15:21:23 UTC

[GitHub] [james-project] ff-wl commented on pull request #886: [JAMES-3715] upgrade to netty 4.1.72.Final

ff-wl commented on pull request #886:
URL: https://github.com/apache/james-project/pull/886#issuecomment-1059256662


   
   > What's weird to me is that it seems allocated by SSLHandler thus logically the SSLHandler is responsible of releasing the buffer, not us. Also from what I could see `ByteToMessageDecoder` manages the buffers for `ImapRequestFrameDecoder` ... Should we try opening a bug report upstream to the Netty project?
   
   The SSL-Handler allocates the Buffer (after decryption) and puts it into the handler queue. Then the next handler is responsible to release the buffer or "fire" it to the next handler. The last handler must release it. With the advanced leak detection level you will see the handling of the responsibility.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@james.apache.org
For additional commands, e-mail: notifications-help@james.apache.org