Bug #46025 [Com]: zend_bailout can deadlock APC

Edit report at https://bugs.php.net/bug.php?id=46025&edit=1 ID: 46025 Comment by: askalski at gmail dot com Reported by: askalski at gmail dot com Summary: zend_bailout can deadlock APC Status: Feedback Type: Bug Package: Reproducible crash Operating System: redhat PHP Version: 5.2.6 Assigned To: gopalv Block user comment: N Private report: N New Comment: Recent versions of APC will also require the patch from bug #59281 in conjunction with the PHP-side patch on this ticket. Previous Comments: ------------------------------------------------------------------------ [2012-05-18 14:55:44] zhangjiayin99 at gmail dot com This issue is still reproducable using php-fpm and PHP 5.3.10 with APC 3.1.9 ------------------------------------------------------------------------ [2011-08-17 21:57:09] pierre at archlinux dot de This issue is still reproducable using php-fpm and PHP 5.3.6 with APC 3.1.9 ------------------------------------------------------------------------ [2010-11-07 21:08:38] felipe@php.net Gopal, this issue has been already fixed? ------------------------------------------------------------------------ [2010-06-24 18:52:07] askalski at gmail dot com A note about the above patches: They work with the stable 3.0.19 release of APC, but not the beta 3.1.3p1. In the beta version, compilation was moved inside a HANDLE_BLOCK_INTERRUPTIONS/HANDLE_UNBLOCK_INTERRUPTIONS block, so the zend_bailout deferral is no longer safe. For example, a syntax error in the script will result in a partially compiled opcode array to be cached in APC. I don't yet have an alternate solution. ------------------------------------------------------------------------ [2010-05-31 06:54:14] askalski at gmail dot com I uploaded patches against the latest 5.1, 5.2, and 5.3 versions of PHP, for sites with production issues that can't afford to wait years for an upstream fix. ------------------------------------------------------------------------ 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=46025 -- Edit this bug report at https://bugs.php.net/bug.php?id=46025&edit=1