Re: useCompression=true and potential Memory leak due to connection tracking via CompressionInputStreamMemoryLeak
Posted by: Alexander Soklakov
Date: May 13, 2013 04:10AM

Hi Dominic,

And great thanks! Your investigation is highly useful. Please look at bug report and patch there. Instead of WeakReference I added connection reference cleanup in CompressedInputStream.close() and see no leak now.

Options: ReplyQuote

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.