Bug #75573 [Com]: Segmentation fault in 7.1.12 and 7.0.26

Edit report at https://bugs.php.net/bug.php?id=75573&edit=1 ID: 75573 Comment by: michael at imagely dot com Reported by: manuel-php at mausz dot at Summary: Segmentation fault in 7.1.12 and 7.0.26 Status: Closed Type: Bug Package: Reproducible crash Operating System: Linux PHP Version: 7.1.12 Block user comment: N Private report: N New Comment: Any sense when this commit/patch will be released? Thanks, Mike. Previous Comments: ------------------------------------------------------------------------ [2017-12-08 18:43:49] ab@php.net Related To: Bug #75651 ------------------------------------------------------------------------ [2017-12-04 10:53:13] ab@php.net Automatic comment on behalf of laruence@gmail.com Revision: http://git.php.net/?p=php-src.git;a=commit;h=d4dee4a6144ff12c6ac4b29968dda13eda406011 Log: Fixed bug #75573 (Segmentation fault in 7.1.12 and 7.0.26) ------------------------------------------------------------------------ [2017-12-01 11:29:30] remi@php.net @laruence, as far as I can see this is only fixed in 7.1+ While 7.0.26 is also affected. ------------------------------------------------------------------------ [2017-12-01 04:49:11] nyseplaya at gmail dot com NextGen gallery worked on my site for months with 7.0.26 why is it suddenly a problem with the PHP? I foolishly updated today without reading the disabling ability. How can I uninstall the latest update? ------------------------------------------------------------------------ [2017-11-30 15:02:58] post at minhost dot no As I commented before, I applied the patch http://git.php.net/?p=php-src.git;a=commit;h=3b9ba7b6bd9e24bdbeca8e8e3f24cee2fccc51d8 and it seemed to fix the bug. However after testing more today, the bug is still present. I don't know if it is the same bug or not, I have filled a bug report here previous https://bugs.php.net/bug.php?id=75579 - anyway the patch did not work after all. What happens is that after visiting about nine wordpress sites (wich by the way was auto-updating from wordpress 4.9 to 4.9.1), then interned strings used memory became full and sites started to go down with HTTP ERROR 500, and apache error log got lines like this: [Thu Nov 30 15:40:40.273796 2017] [proxy_fcgi:error] [pid 17990:tid 140238684755712] [client 176.74.214.18:42343] AH01071: Got error 'PHP message: PHP Fatal error: Cannot declare interface JsonSerializable, because the name is already in use in /home/USER/domains/DOMAIN.TLD/public_html/wp-includes/compat.php on line 428\n' [Thu Nov 30 15:40:41.697018 2017] [proxy_fcgi:error] [pid 17990:tid 140238693148416] [client 176.74.214.18:52760] AH01071: Got error 'PHP message: PHP Fatal error: Cannot declare interface JsonSerializable, because the name is already in use in /home/USER/domains/DOMAIN.TLD/public_html/wp-includes/compat.php on line 428\n' In PHP info page it looks like this when interned strings used memory become full (and sites stop working!): Interned Strings Used memory 4194288 Interned Strings Free memory 16 This is a completely show stoppper wich makes PHP 7.1.12 not usable. Some developers at PHP really need to take time to look deep into this now. It is a critical bug introduced in PHP 7.1.12 and (possibly 7.0.26) if you use opcache, wich forces you to stay on PHP 7.1.11 wich do not have this bug. Can someone at PHP please understand the seriousness in this? Please study both this bug #75573 and my bug report #75579, they could be the same thing, or separate issues but somehow related. ------------------------------------------------------------------------ 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=75573 -- Edit this bug report at https://bugs.php.net/bug.php?id=75573&edit=1