Memory leak

[resostandards]

Memory leak

[JacobEdmondKerr]

I am having issues with a memory leak via CURL. I'm not sure if it's my PHP version? I'm using PHP Version 5.5.38. SteveMullen did you find a solution to this problem?

The line that is using the memory is line 185 in CurlClient.php: $rbody = curl_exec($this->curl); I have read that CURL has issues with CURLOPT_RETURNTRANSFER in some versions of PHP.

[SteveMullen]

Hi Jacob - I don't use the RESO\RESO api anymore, because there were a few problems I couldn't solve. I ended up writing my own code.

[abiggrboat]

I just started using the reso api client and have noticed the same issue. It's not possible to retrieve larger numbers of records in a loop without exhausting all available memory. It turns out the culprit is the request member function is initializing the curl client on every call. I revised the request class (i.e. in my copy) to persist the curl object and only initialize it once and the memory leak is gone.

[redtailmatt]

I've noticed that the RESO\HttpClient\CurlClient is never closed in RESO\Request::request() or ::requestPost().
Have you tried adding $curl->close(); before the return line of the request functions? This significantly reduced the memory usage for me.