Doc #75247 [Com]: Documentation Recommends Broken Setting

Edit report at https://bugs.php.net/bug.php?id=75247&edit=1 ID: 75247 Comment by: pegasus at vaultwiki dot org Reported by: pegasus at vaultwiki dot org Summary: Documentation Recommends Broken Setting Status: Open Type: Documentation Problem Package: opcache PHP Version: 5.6.31 Block user comment: N Private report: N New Comment: See also this PHP bug report, providing case-in-point, which has gone ignored for over 2 years even though the requested information was provided: https://bugs.php.net/bug.php?id=69190 Previous Comments: ------------------------------------------------------------------------ [2017-09-22 19:25:22] pegasus at vaultwiki dot org Description: ------------ --- From manual page: http://www.php.net/opcache.installation --- The page recommends using directive opcache.fast_shutdown = 1, however this directive is known to be broken. See the following Zend bug which has remained unsolved since 2013: https://github.com/zendtech/ZendOptimizerPlus/issues/146 In my experiences on many clients' servers, fast_shutdown occasionally caused PHP<->web server communication to fail and the PHP process to crash in random places without a segfault. In a number of cases, this led to database corruption. Disabling opcache.fast_shutdown always resolved the issue. Since opcache.fast_shutdown bypasses PHP garbage collection in favor of Zend MM garbage collection, it is likely that Zend MM is not doing this successfully, possibly creating a Use-Again-Without-Free? situation which causes the next process to crash. However, without segfaults to provide information, this is only a theory. Expected result: ---------------- The documentation should not recommend opcache.fast_shutdown = 1 until the Zend bug is fixed: https://github.com/zendtech/ZendOptimizerPlus/issues/146 If the Zend bug is fixed, the documentation should specify which version(s) of PHP the fix applies in, and therefore which version of PHP opcache.fast_shutdown becomes safe to use again. ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=75247&edit=1