Bug #68486 [Com]: PHP SegFault zend_hash_find

Edit report at https://bugs.php.net/bug.php?id=68486&edit=1 ID: 68486 Comment by: phpdev at ehrhardt dot nl Reported by: wattwood at tcstire dot com Summary: PHP SegFault zend_hash_find Status: Open Type: Bug Package: Apache2 related Operating System: Ubuntu 14.04.1 LTS PHP Version: 5.5.19 Block user comment: N Private report: N New Comment: The same one-liner fixed segfaults in Apache 2.4.12 64-bit on Windows 2008 R2 with PHP 5.6.7 64-bit as mod_php. I could make it segfault from a remote Linux server... Previous Comments: ------------------------------------------------------------------------ [2015-03-19 18:59:04] php at bof dot de Related To: Bug #69218 ------------------------------------------------------------------------ [2015-03-19 14:58:20] phpdev at ehrhardt dot nl I applied the 1 line patch at https://bugs.php.net/patch-display.php?bug_id=68486&patch=sapi_apache2.gmoniker.patch&revision=latest to my Centos6, Apache 2.4.12 with PHP 5.6.6 as mod_php and the segfaults vanished as well. ------------------------------------------------------------------------ [2015-03-19 07:52:51] php at bof dot de Everything is running smoothly with the one-line patch attached yesterday (thanks again gmoniker!). That is on two different (same load) production boxes, one with Apache 2.2 and one with Apache 2.4. No segfaults, no CPU usage or memory usage or latency issues (I've got them covered pretty thoroughly in Nagios). I think this is ready to go into the next 5.5.x, 5.6.x, and master. ------------------------------------------------------------------------ [2015-03-18 22:39:33] gmoniker at gmail dot com @bof, Thanks for your hard work! I still don't know exactly when the first request pool is destroyed by the EOR bucket. It might be when the output of the next request begins to run. Anyway this is a very necessary patch for using Apache 2.4. ------------------------------------------------------------------------ [2015-03-18 15:29:10] php at bof dot de Production test of the one-liner patch, using Apache 2.4, ran flawlessly, now for five hours straight. Just to be sure it's good, I'll run a second build under Apache 2.2 + put that on one of my not-yet-upgraded production servers tomorrow. But I think this patch is good to go in. I added it now as a patch to this bug report, for that reason. ------------------------------------------------------------------------ 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=68486 -- Edit this bug report at https://bugs.php.net/bug.php?id=68486&edit=1