Edit report at https://bugs.php.net/bug.php?id=63516&edit=1
ID: 63516 Comment by: arjen at react dot com Reported by: dpeuscher at gmail dot com Summary: The Process exits random with SEGV Status: Open Type: Bug Package: SOAP related Operating System: openSUSE 11.0 (X86-64) PHP Version: 5.4.8 Block user comment: N Private report: N New Comment: Does not crash with WSDL_CACHE_DISK, DOES crash with WSDL_CACHE_MEMORY. Previous Comments: ------------------------------------------------------------------------ [2013-06-06 15:59:48] dpeuscher at gmail dot com Accidentally changed the package to apache2-related, sorry. ------------------------------------------------------------------------ [2013-06-06 15:57:51] dpeuscher at gmail dot com Have you tried the WSDL_CACHE_DISK caching method instead of WSDL_CACHE_BOTH? ------------------------------------------------------------------------ [2013-06-06 11:25:48] arjen at react dot dom I can confirm this under 5.4.15, got the same backtrace using the testscript. ------------------------------------------------------------------------ [2012-11-15 14:16:07] dpeuscher at gmail dot com That was a great hint. I got it isolated! It seams like the problem occurs when the ini-option wsdl_cache is set to 3 (WSDL_CACHE_BOTH), maybe also 2 (WSDL_CACHE_MEMORY). I initialized 5 WSDL-Files that are nearly empty (just to don't throw any exceptions like "Could not find any usable binding services in WSDL.". They all look like this: http://pastebin.com/e6QBUkeh (Wasn't allowed to put it in here because of possible Spam) with 5 different names. I named them s1.wsdl, ... s5.wsdl. Afterwards I initialized an ebay-Webservice. The test-Script looks like this: http://pastebin.com/dWxg1qL7 Sometimes the SEGV appears after 50 calls, sometimes on the first call. It doesn't apper on WSDL_CACHE_DISK or WSDL_CACHE_NONE. ------------------------------------------------------------------------ [2012-11-15 00:00:05] fel...@php.net Please, try isolating the SOAP related part of code. ------------------------------------------------------------------------ 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=63516 -- Edit this bug report at https://bugs.php.net/bug.php?id=63516&edit=1
