Bug #78103 [Opn->Csd]: Allocating ~2TB memory after PHP_FCGI_CHILDREN-th request

Edit report at https://bugs.php.net/bug.php?id=78103&edit=1 ID: 78103 Updated by: cmb@php.net Reported by: hardaqa at gmail dot com Summary: Allocating ~2TB memory after PHP_FCGI_CHILDREN-th request -Status: Open +Status: Closed Type: Bug Package: CGI/CLI related Operating System: Windows 10 v1809 64bit PHP Version: 7.2.19 -Assigned To: +Assigned To: cmb Block user comment: N Private report: N New Comment: > This does not happen anymore in 7.2.20 for me. Okay, closing then. Previous Comments: ------------------------------------------------------------------------ [2019-07-03 22:21:20] hardaqa at gmail dot com This does not happen anymore in 7.2.20 for me. ------------------------------------------------------------------------ [2019-06-19 00:59:50] jbrady at sbccd dot edu This happened for us on IIS using FastCGI with both Windows 2008 R2 & Windows 2012 R2. It can be fixed by going back to 7.2.18 or explicitly disabling opcache (opcache.enabled=0). This was verified in phpinfo and by explicitly changing the php.ini. ------------------------------------------------------------------------ [2019-06-14 09:57:16] mario dot bandeira at cronobandeira dot com Yes, I have double check with phpinfo() that opcache was disable. As I am not an expert on web systems, here the complete system config for your evaluation: Windows server 2016, IIS, plesk Onyx 17.8.11 update#55, php7.2.19 (with php7.1.30 works ok), testing subdomain. ------------------------------------------------------------------------ [2019-06-13 08:23:18] nikic@php.net I can't reproduce this on Linux, with or without opcache. Possibly Windows-only? ------------------------------------------------------------------------ [2019-06-12 19:53:37] cmb@php.net Have you double-checked (e.g. via phpinfo()) that Opcache is indeed disabled? ------------------------------------------------------------------------ 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=78103 -- Edit this bug report at https://bugs.php.net/bug.php?id=78103&edit=1