We are using grizzly (version 2.3.21) to perform some HTTP requests. After those requests have finished, in a thread dump i can still see the response objects being referenced, and not being garbage collected. Attached is a screenshot of there references from a heap dump:
In a case where the size of the transferred data is big, i see some heavy memory usage.
Question is, are those references held on purpose and would be removed eventually as the application runs or is this a bug that could potentially cause a memory leak? In any way, i would expect these objects to not be held by the connection once the http transfer has finished.
Thanks in advance,
could you pls. create an issue and link the testcase, so we can look into that?
On 12/21/15 12:24 PM, Rodrigo Merino wrote:
While building the testcase, i found that the problem happens only when using grizzly + AHC. When using grizzly alone it doesn't happen.
I have created an issue in AHC for this: https://github.com/AsyncHttpClient/async-http-client/issues/1067
On Mon, Dec 21, 2015 at 5:34 PM, Oleksiy Stashok <[hidden email]> wrote:
|Free forum by Nabble||Edit this page|