go to bug id or search bugs for
I cannot instantiate a single SoapClient instance, without getting a memory error.
I raised memory_limit to 1GB, but this didn't change anything: now the library tries to allocate 1.5GB of memory for some obscure reason.
Note that this occurs *before* the SOAP client downloads the WSDL file, as I get this exception in less than 1ms.
SoapFault exception: [Client] Allowed memory size of 1073741824 bytes exhausted (tried to allocate 1644167200 bytes)
Add a Patch
Add a Pull Request
Actually this bug had already been reported as far as in PHP 7.0.0alpha2, but due to the original reporter not answer the question, it's been closed:
But it's definitely still present in RC7.
Hopefully you'll be able to reproduce it with this one-liner.
@benjamin Thanks for the repro case.
So far I was checking, same is reproduceable with 5.6 as well. It has something to do with serealization/deserealization of WSDL. Only reproduceable on second call after the cached WSDL gets deserialized, so soap.wsdl_cache_dir=/some/valid/dir is required to repro.
Automatic comment on behalf of firstname.lastname@example.org
Log: Fixed bug #70900 (SoapClient systematic out of memory error)
you'll have to manually clean WSDL cache (rm /tmp/wsdl-*) after update.
@dmitry, works a treat with your latest commit! Thanks so much.