Bug #71931 [Opn]: Soap cache_wsdl WSDL_CACHE_MEMORY option on CLI

Edit report at https://bugs.php.net/bug.php?id=71931&edit=1 ID: 71931 Updated by: nikic@php.net Reported by: nikspijkerman at gmail dot com Summary: Soap cache_wsdl WSDL_CACHE_MEMORY option on CLI Status: Open Type: Bug Package: SOAP related Operating System: Ubuntu 14.04 PHP Version: 7.0.4 Block user comment: N Private report: N New Comment: Based on the backtrace (and the fact that it only happens when the WSDL memory cache is enabled) this is very likely the same issue as bug #75502, which is now fixed. Previous Comments: ------------------------------------------------------------------------ [2017-11-16 14:18:19] mike dot grinspan at gmail dot com Issue persists on ubuntu 17.04 (zesty) with PHP 7.1.11 (ondrej/php) ------------------------------------------------------------------------ [2017-06-08 17:19:32] nunojsferreira at gmail dot com I am experiencing the exact same problem in a containerized symfony app based on docker image from docker hub php:7.1-apache more specifically PHP 7.1.5 (cli) (built: May 13 2017 00:13:21) ( NTS ) When disabling the WSDL_CACHE_BOTH to just DISK or NONE seem to prevent the issue from happening. I was experiencing the problem randomly. CURLing the exact same request could segfault or not. Probably not relevant but its also a symfony 2.8 app. ------------------------------------------------------------------------ [2017-05-15 14:37:31] tech at enuygun dot com Issue still exists in 7.1.4 and 7.1.5, debian jessie with sury php packages. ------------------------------------------------------------------------ [2017-01-27 07:58:38] tentje at gmail dot com The issue persists in PHP 7.1.1 ------------------------------------------------------------------------ [2016-11-24 03:32:21] bddenhartog at gmail dot com I have this same issue running PHP-CGI under IIS. The server is Windows Server 2012 R2 Datacenter. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at https://bugs.php.net/bug.php?id=71931 -- Edit this bug report at https://bugs.php.net/bug.php?id=71931&edit=1