Bug #66460 [Com]: PHP 5.5.7 and 5.5.8 horrible unstable

From: Date: Fri, 10 Jan 2014 19:21:35 +0000
Subject: Bug #66460 [Com]: PHP 5.5.7 and 5.5.8 horrible unstable
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-183704@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=66460&edit=1 ID: 66460 Comment by: spam2 at rhsoft dot net Reported by: spam2 at rhsoft dot net Summary: PHP 5.5.7 and 5.5.8 horrible unstable Status: Open Type: Bug Package: opcache Operating System: Linux PHP Version: 5.5.8 Block user comment: N Private report: N New Comment: crap - on the machine in front of me it makes no differnce how i configure opcache, it crashed right after restart and never generated a single page of our self-developed cms, after restart httpd and open phpMyAdmin i wondered that this did not crash and after that for now it appears that my cms-page also runs stable this is completly unpredictable and i doubt that the other reporter which confirmed this behavior and me are the only persons facing this whatever changes are done to "opcache" they are broken [zend] zend_extension = "/usr/lib64/php/modules/opcache.so" opcache.enable = 1 opcache.enable_cli = 0 opcache.load_comments = 0 opcache.save_comments = 0 opcache.use_cwd = 1 opcache.validate_timestamps = 1 opcache.revalidate_freq = 5 opcache.revalidate_path = 1 opcache.max_accelerated_files = 1000 opcache.memory_consumption = 128 opcache.interned_strings_buffer = 8 opcache.max_file_size = 262144 opcache.enable_file_override = 0 opcache.fast_shutdown = 1 opcache.error_log = "/var/log/php_error.log" opcache.log_verbosity_level = 1 Previous Comments: ------------------------------------------------------------------------ [2014-01-10 19:05:26] spam008 at evil dot net dot pl I have EXEACLY same observation. It only happens on three vhosts running Typo3 (multiple versions). It happens on both of my WWW servers. Im going back to 5.5.5 right now. Im using opcache too. PHP-FPM self compiled on Slackware64 14.1. One of my opcache`s config: zend_extension = "opcache.so" opcache.memory_consumption = 256 opcache.interned_strings_buffer = 8 opcache.max_accelerated_files = 10000 opcache.revalidate_freq = 0 opcache.validate_timestamps = On opcache.fast_shutdown = Off opcache.enable = On opcache.enable_cli = Off opcache.max_file_size = 0 opcache.use_cwd = On opcache.log_verbosity_level = 2 opcache.load_comments = On opcache.save_comments = On ------------------------------------------------------------------------ [2014-01-10 19:00:54] spam2 at rhsoft dot net OK, i come tighter to the circumstances on the machine where it permanently crahed for now re-enable "opcache.revalidate_path" seems to workarund the problem, but i am far away to trust because it's too unpredictable on different machines / websites using the same core-codebase of our applications ___________________________________________________ for now stable or at least more stable [zend] zend_extension = "/usr/lib64/php/modules/opcache.so" opcache.enable = 1 opcache.enable_cli = 0 opcache.load_comments = 0 opcache.save_comments = 0 opcache.use_cwd = 1 opcache.validate_timestamps = 1 opcache.revalidate_freq = 5 opcache.revalidate_path = 1 opcache.max_accelerated_files = 200 opcache.memory_consumption = 16 opcache.max_file_size = 262144 opcache.enable_file_override = 0 opcache.fast_shutdown = 1 opcache.error_log = "/www/_logs/php_error.log" opcache.log_verbosity_level = 1 ___________________________________________________ previous config which was stable over months [zend] zend_extension = "/usr/lib64/php/modules/opcache.so" opcache.enable = 1 opcache.enable_cli = 0 opcache.load_comments = 0 opcache.save_comments = 0 opcache.use_cwd = 1 opcache.validate_timestamps = 1 opcache.revalidate_freq = 5 opcache.revalidate_path = 0 opcache.max_accelerated_files = 200 opcache.memory_consumption = 16 opcache.max_file_size = 262144 opcache.enable_file_override = 1 opcache.fast_shutdown = 1 opcache.error_log = "/www/_logs/php_error.log" opcache.log_verbosity_level = 1 ------------------------------------------------------------------------ [2014-01-10 18:54:17] spam2 at rhsoft dot net maybe the real configuration helps to reproduce i would appreciate a unified diff for "rpmbuild" with reverts the latest opcache changes to the state of 5.5.6 and matching the 5.5.8 tarball to provide feedback in the meantime i try to reproduce it with a small script instead a large application, at the moment i am out of ideas [zend] zend_extension = "/usr/lib64/php/modules/opcache.so" opcache.enable = 1 opcache.enable_cli = 0 opcache.load_comments = 0 opcache.save_comments = 0 opcache.use_cwd = 1 opcache.validate_timestamps = 1 opcache.revalidate_freq = 5 opcache.revalidate_path = 0 opcache.max_accelerated_files = 200 opcache.memory_consumption = 16 opcache.max_file_size = 262144 opcache.enable_file_override = 0 opcache.fast_shutdown = 1 opcache.error_log = "/www/_logs/php_error.log" opcache.log_verbosity_level = 1 ------------------------------------------------------------------------ [2014-01-10 18:39:28] spam2 at rhsoft dot net Description: ------------ PHP 5.5.6 is running fine with opcache PHP 5.5.7 and 5.5.8 [Fri Jan 10 19:31:12.026088 2014] [core:notice] [pid 17100] AH00052: child pid 17108 exit signal Segmentation fault (11) [Fri Jan 10 19:31:13.027956 2014] [core:notice] [pid 17100] AH00052: child pid 17142 exit signal Segmentation fault (11) [Fri Jan 10 19:31:14.030639 2014] [core:notice] [pid 17100] AH00052: child pid 17150 exit signal Segmentation fault (11) [Fri Jan 10 19:31:14.030679 2014] [core:notice] [pid 17100] AH00052: child pid 17151 exit signal Segmentation fault (11) [Fri Jan 10 19:31:15.034780 2014] [core:notice] [pid 17100] AH00052: child pid 17152 exit signal Segmentation fault (11) [Fri Jan 10 19:31:15.034820 2014] [core:notice] [pid 17100] AH00052: child pid 17153 exit signal Segmentation fault (11) [Fri Jan 10 19:31:15.034827 2014] [core:notice] [pid 17100] AH00052: child pid 17154 exit signal Segmentation fault (11) [Fri Jan 10 19:31:15.034834 2014] [core:notice] [pid 17100] AH00052: child pid 17155 exit signal Segmentation fault (11) [Fri Jan 10 19:31:16.038616 2014] [core:notice] [pid 17100] AH00052: child pid 17156 exit signal Segmentation fault (11) [Fri Jan 10 19:31:16.038652 2014] [core:notice] [pid 17100] AH00052: child pid 17157 exit signal Segmentation fault (11) [Fri Jan 10 19:31:17.042936 2014] [core:notice] [pid 17100] AH00052: child pid 17159 exit signal Segmentation fault (11) [Fri Jan 10 19:31:17.042968 2014] [core:notice] [pid 17100] AH00052: child pid 17160 exit signal Segmentation fault (11) _________________________________________ on one of my testing-machines disable "opcache.enable_file_override" which was enabled with PHP 5.4 all the time makes it better, on another server no way - permenently segfaults until i stop to load opcache the really strange is that with "ab -c 100 -n 50000" i am unable to reprocude a single segfault, sometimes depending on luck also not with browsing, the next time nearly any request is answered with a Firefox error that the server unexpectly closed the connection Test script: --------------- currently i have no easy test-script, only cms pages and complexer libraries used and as said: it may take hours to reproduce and in other cases i update a production server to PHP > 5.5.6 and it gets terrible unstable shortly after restart httpd ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=66460&edit=1

« previous php.bugs (#183704) next »