You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
The CurlHttpClient has a memory leak which seems to have been caused by this PR #35674 .
When an exception occurs the CurlResponse::close method never gets called from __destruct cause of the PR & the handler never gets unset from the CurlClientState::$openHandles & CurlClientState::$handlesActivity arrays. Over time this leads to a lot of handlers piling up in the memory, causing a memory leak. I've notice this while using the HttpClient in a Messenger handler.
Symfony version(s) affected: 4.4
Description
The
CurlHttpClient
has a memory leak which seems to have been caused by this PR #35674 .When an exception occurs the
CurlResponse::close
method never gets called from__destruct
cause of the PR & the handler never gets unset from theCurlClientState::$openHandles
&CurlClientState::$handlesActivity
arrays. Over time this leads to a lot of handlers piling up in the memory, causing a memory leak. I've notice this while using the HttpClient in a Messenger handler.How to reproduce
Additional context
The text was updated successfully, but these errors were encountered: