Bug #77312 [Csd]: accel_replace_string_by_process_permanent: Assertion `0' failed

Edit report at https://bugs.php.net/bug.php?id=77312&edit=1 ID: 77312 User updated by: sjon at hortensius dot net Reported by: sjon at hortensius dot net Summary: accel_replace_string_by_process_permanent: Assertion `0' failed Status: Closed Type: Bug Package: opcache Operating System: archlinux PHP Version: 7.3.0 Block user comment: N Private report: N New Comment: @lauri thanks for the hint - I already did that and was still unsuccessful. I'm happy to see if it still happens in 7.3.1 and reopen this bug if it does Previous Comments: ------------------------------------------------------------------------ [2019-01-10 18:06:28] lauri dot kentta at gmail dot com @sjon, GDB detaches from forked processes by default. You can use "set follow-fork-mode child" or "set detach-on-fork off" to debug the php-fpm child processes. Also, just saying: since this bug was basically about a string not being found, it could have been the one I mentioned (which caused memory corruption and sometimes invalid string values). But no matter. ------------------------------------------------------------------------ [2019-01-10 12:01:30] sjon at hortensius dot net This seems to be fixed in 7.3.1 - and while it happens frequently I cannot seem to obtain a coredump or get gdb to catch it - closing for now ------------------------------------------------------------------------ [2019-01-09 09:05:58] nikic@php.net Could you please provide a backtrace for the assertion failure? That way we'd know which string it is trying to replace. ------------------------------------------------------------------------ [2019-01-09 08:50:59] sjon at hortensius dot net @lauri thanks for trying - but we don't use persistent MySQL connections in our code. I also find it highly unlikely that could cause opcache errors ------------------------------------------------------------------------ [2019-01-07 19:29:04] lauri dot kentta at gmail dot com This could be related to bug #77289. In that case, disabling persistent MySQL connections should fix it. Can you try that? ------------------------------------------------------------------------ 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=77312 -- Edit this bug report at https://bugs.php.net/bug.php?id=77312&edit=1