Bug #75621 [Com]: Opcache crashes Apache possible with bad chars

Edit report at https://bugs.php.net/bug.php?id=75621&edit=1 ID: 75621 Comment by: pascal dot nobus at webservice dot be Reported by: pascal dot nobus at webservice dot be Summary: Opcache crashes Apache possible with bad chars Status: Feedback Type: Bug Package: opcache Operating System: Slackware 14.1 PHP Version: 7.1.12 Block user comment: N Private report: N New Comment: I'm running 7.1.13RC1 now for almost 20h without a single core-dump. So it looks the problem is solved! If it's up to me you may consider bug#75261 bug#75573 bug#75579 as CLOSED. Previous Comments: ------------------------------------------------------------------------ [2017-12-17 21:24:06] nikic@php.net This is most likely bug #75573. Can you check whether 7.1.13RC1 resolves this issue? ------------------------------------------------------------------------ [2017-12-13 12:53:53] pascal at nobus dot Be I have been collecting coredump since a few days, and I see about 2 crashes a day. The all have different files now? P.S. I run nginx as a proxy before this apache, could this have something to do with it? (don't see any problems with nginx) #0 i_zval_ptr_dtor (zval_ptr=0x7fd3f024aa40) at /usr/local/src/php-7.1.12/Zend/zend_variables.h:46 46 if (Z_REFCOUNTED_P(zval_ptr)) { #0 zend_hash_clean (ht=0x7fd48a02ae78) at /usr/local/src/php-7.1.12/Zend/zend_hash.c:1366 1366 if (EXPECTED(Z_TYPE(p->val) != IS_UNDEF)) { #0 zend_hash_clean (ht=0x7fd4880c7690) at /usr/local/src/php-7.1.12/Zend/zend_hash.c:1352 1352 if (EXPECTED(Z_TYPE(p->val) != IS_UNDEF)) { #0 zval_delref_p (pz=<optimized out>, pz=<optimized out>) at /usr/local/src/php-7.1.12/Zend/zend_types.h:838 838 return --GC_REFCOUNT(Z_COUNTED_P(pz)); #0 execute_ex (ex=<optimized out>) at /usr/local/src/php-7.1.12/Zend/zend_vm_execute.h:429 429 ((opcode_handler_t)OPLINE->handler)(ZEND_OPCODE_HANDLER_ARGS_PASSTHRU); #0 execute_ex (ex=<optimized out>) at /usr/local/src/php-7.1.12/Zend/zend_vm_execute.h:429 429 ((opcode_handler_t)OPLINE->handler)(ZEND_OPCODE_HANDLER_ARGS_PASSTHRU); ------------------------------------------------------------------------ [2017-12-05 10:44:00] post at minhost dot no Strange that you don't see statistic for opcache on a phpinfo page, like "Interned Strings Used memory" and "Interned Strings Free memory", maybe it is because you run PHP as a module. I run PHP as FPM, so I don't know. What I see in PHP 7.1.12 is that Interned Strings memory run full in a very short time, then PHP pages start to go down. What I don't know if Interned Strings Free memory is supposed to run full in a short time or not? It never happened before, it was always plenty memory left in Interned Strings Free memory before upgrading to PHP 7.1.12. Question is if that was a bug before or not. Only thing I can say for sure, is that when there is no Interned Strings Free memory left in PHP 7.1.12, then PHP pages go down. That never happened in previous PHP versions. I have set opcache.interned_strings_buffer to 4, and by the way that is the default value according to http://php.net/manual/en/opcache.configuration.php I am worried about lack of response to from PHP developers to Bug #75579, my fear is that this will not be fixed anytime soon, so that I will be stuck on PHP 7.1.11 ------------------------------------------------------------------------ [2017-12-05 10:12:31] pascal dot nobus at webservice dot be The apache-logs show it was an apache-child that got the Segmentation fault: [Sun Dec 03 15:21:44.025975 2017] [core:notice] [pid 29980:tid 140454601000832] AH00052: child pid 4005 exit signal Segmentation fault (11) but that's quit normal because php is configured as a module (not fpm). According to the symptons it looks to me that it is related to bug 75579. However I can't see Interned Strings Used/Free memory, it's not in my phpinfo, nor in opcache_get_status I also have the default value for interned_strings_buffer opcache.interned_strings_buffer=8 ------------------------------------------------------------------------ [2017-12-05 09:05:57] post at minhost dot no Are you sure it is Apache that crashes and not only PHP pages? If it is only PHP pages that crashes, then it could be related to Bug #75579 ------------------------------------------------------------------------ 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=75621 -- Edit this bug report at https://bugs.php.net/bug.php?id=75621&edit=1