Open averysadonion opened 1 year ago
Hey, thats a problem in the golang library. We'll have to wait for bogdanfinn to fix it.
@FlorianREGAZ the golang library already exposes the functions freeMemory
, destroySession
and destroyAll
.
The readme also tackles the issue of not freeing the responses here: (https://github.com/bogdanfinn/tls-client#compile-this-client-as-a-shared-library-for-use-in-other-languages-like-python-or-nodejs)
With this, closing the response after retrieving all necessary values is already possible.
I have this problem. Is there a solution?
internal buffer error : Memory allocation failed : growing buffer fatal error: runtime: C malloc failed
Is there a solution yet? Still has memory leaks
My program runs multiple threads of a function performing a get request, and although the number of threads remains constant throughout the program, the memory usage and object count gradually increases over time until no free memory is left on the system. After doing some digging I found that base requests library has some memory leaking issues with the response object that can be fixed by using .close() method on the session and response like so:
I can't seem to find a solution to solving this issue within this library.
Sample code: