Bug #71182 [Opn->Csd]: SIGSEGV at php-fpm 7.0.1

Edit report at https://bugs.php.net/bug.php?id=71182&edit=1 ID: 71182 Updated by: krakjoe@php.net Reported by: mfractal at gmail dot com Summary: SIGSEGV at php-fpm 7.0.1 -Status: Open +Status: Closed Type: Bug Package: FPM related Operating System: Ubuntu 14.04.3 LTS PHP Version: 7.0.1 -Assigned To: +Assigned To: krakjoe Block user comment: N Private report: N New Comment: Since this was reported to be fixed nearly a year ago, I'm closing this. Previous Comments: ------------------------------------------------------------------------ [2016-01-29 10:40:53] venancio1981 at gmail dot com Since php 7.0.2 i don't have the segfaults anymore. Its seems fixed for me. ------------------------------------------------------------------------ [2016-01-29 10:35:50] steffen dot weber at gmail dot com Please ignore parts of my previous comment. The SIGSEGV exits have only occured once after upgrading from PHP 5.6 to 7.0. Now I'm seeing normal "exited with code 0" logs again. Maybe the hint about "pm.max_requests" can help others. ------------------------------------------------------------------------ [2016-01-29 09:23:27] steffen dot weber at gmail dot com Since upgrading from PHP 5.6 to 7.0 I'm seeing "exited on signal 11 (SIGSEGV)" warnings instead of "exited with code 0" notices in my php-fpm error log at intervals that I can influence by changing "pm.max_requests". So I guess that the SIGSEGV happens when PHP 7.0 tries to exit cleanly after having served "pm.max_requests". ------------------------------------------------------------------------ [2015-12-21 17:06:43] frej dot akki at gmail dot com Same here, i also see the same error from the coredump centos 6.7 ------------------------------------------------------------------------ [2015-12-21 15:14:33] venancio1981 at gmail dot com Im also seing this error in the php-fpm error logs using php 7.0.1. I use Centos 7.2. In my case, the segfault happens more or less each hour in every child. ------------------------------------------------------------------------ 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=71182 -- Edit this bug report at https://bugs.php.net/bug.php?id=71182&edit=1