Bug #78147 [Com]: Memory leak after upgrade to 7.2.19

Edit report at https://bugs.php.net/bug.php?id=78147&edit=1 ID: 78147 Comment by: kris at accuwebhosting dot com Reported by: mario dot bandeira at cronobandeira dot com Summary: Memory leak after upgrade to 7.2.19 Status: Open Type: Bug Package: opcache Operating System: Windows Server 2016 Standard PHP Version: 7.2.19 Block user comment: N Private report: N New Comment: Same issue with PHP 7.2.19 (FastCGI), Windows 2016 server and Plesk. Previous Comments: ------------------------------------------------------------------------ [2019-06-12 16:49:31] mendel at spotlightdesign dot com PHP error log: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 7810770492979178392 bytes) ... (That's a lot of bytes!!!, Much more than in the other reports posted). Possibly related to https://bugs.php.net/bug.php?id=78103 (as posted by mario on that report). ------------------------------------------------------------------------ [2019-06-12 15:43:17] mario dot bandeira at cronobandeira dot com I have made some tests and the problem is on with or without the opcache enabled for the subdomain. The subdomain (cnr.cronobandeira.com) that originally had the problem (with php 7.2.19) is now running php 7.1.30 without any issues. ------------------------------------------------------------------------ [2019-06-12 14:48:00] mario dot bandeira at cronobandeira dot com Yes, opcache is enabled. ------------------------------------------------------------------------ [2019-06-12 14:21:06] mendel at spotlightdesign dot com Same issue, a few more details. Windows 2012/IIS/Plesk Onyx 17.8.11 Several websites with no recent changes, only change is plesk updating PHP 7.2 to 7.2.19 https://docs.plesk.com/release-notes/onyx/change-log/#contents-17811-mu55 Yes it is using opcache. ------------------------------------------------------------------------ [2019-06-11 19:39:13] nikic@php.net Are you using opcache? ------------------------------------------------------------------------ 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=78147 -- Edit this bug report at https://bugs.php.net/bug.php?id=78147&edit=1