Bug #73381 [Opn]: Mysterious fpm coredump

Edit report at https://bugs.php.net/bug.php?id=73381&edit=1 ID: 73381 User updated by: lsn at nuvopoint dot com Reported by: lsn at nuvopoint dot com Summary: Mysterious fpm coredump Status: Open Type: Bug Package: FPM related Operating System: Ubuntu 16.04.1 LTS PHP Version: 7.0.12 Block user comment: N Private report: N New Comment: Managed to decode some of the crash file: Program terminated with signal SIGSEGV, Segmentation fault. #0 0x00007fd5839b16a6 in pcre_exec () from /lib/x86_64-linux-gnu/libpcre.so.3 Previous Comments: ------------------------------------------------------------------------ [2016-10-24 10:58:01] lsn at nuvopoint dot com Description: ------------ FPM makes a coredump, which is captured to /var/crash. The coredump file can be found here: https://cloud.nuvoweb.dk/_usr_sbin_php-fpm7.0.33.crash I've just started debugging this, and I have zero experience reading these crash files, so I can't report much. What I can tell is that its running on Ubuntu 16 with all the latest upgrades (as of today), on Nginx 1.11.5. No errors in any logs, be it syslog, nginx-error.log, php's log. The only hint is an error in php-fpm: [24-Oct-2016 09:44:03] NOTICE: fpm is running, pid 1057 [24-Oct-2016 09:44:03] NOTICE: ready to handle connections [24-Oct-2016 09:44:03] NOTICE: systemd monitor interval set to 10000ms [24-Oct-2016 10:06:04] WARNING: [pool www] child 1371 exited on signal 11 (SIGSEGV - core dumped) after 1321.212667 seconds from start I can reproduce it on our setup, using Postman, but if we could decode the crash log above, that might reveal if that is even necessary. I'm available to debug this if needed. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=73381&edit=1