Bug #75492 [Fbk->NoF]: Massive memory allocation

From: Date: Sun, 24 Jun 2018 04:25:37 +0000
Subject: Bug #75492 [Fbk->NoF]: Massive memory allocation
References: 1  Groups: php.bugs 
Request: Send a blank email to php-bugs+get-215916@lists.php.net to get a copy of this message
Edit report at https://bugs.php.net/bug.php?id=75492&edit=1

 ID:               75492
 Updated by:       php-bugs@lists.php.net
 Reported by:      nick at nickstallman dot net
 Summary:          Massive memory allocation
-Status:           Feedback
+Status:           No Feedback
 Type:             Bug
 Package:          FPM related
 Operating System: Ubuntu
 PHP Version:      7.1.11
 Private report:   N

 New Comment:

No feedback was provided. The bug is being suspended because
we assume that you are no longer experiencing the problem.
If this is not the case and you are able to provide the
information that was requested earlier, please do so and
change the status of the bug back to "Re-Opened". Thank you.


Previous Comments:
------------------------------------------------------------------------
[2017-11-07 19:53:48] adambaratz@php.net

When I ran into an issue like this, it was a result of an extension writing to memory that it
shouldn't have. Basically, the value for a string length got corrupted and then this happened.
Unless you're really comfortable with gdb, my general suggestion would be to try disabling
non-core extensions to try to narrow it down. You could also try disabling the PCRE JIT.

------------------------------------------------------------------------
[2017-11-06 23:21:16] nick at nickstallman dot net

Unfortunately I can't seem to reproduce it to get a backtrace.

PHP modules are here: https://gist.github.com/NickStallman/f271375225a99918bd72ebfacdb58cdc
Nothing too unusual. The opcache is enabled.

------------------------------------------------------------------------
[2017-11-06 22:51:59] danack@php.net

HI Nick,

Please could you list the modules loaded by running php -m

Also, please could you generate a backtrace with the instructions from https://bugs.php.net/bugs-generating-backtrace.php

------------------------------------------------------------------------
[2017-11-06 22:41:51] nick at nickstallman dot net

Description:
------------
I just had the following error which is so ridiculous it's not funny:


Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 5826880341616844800
bytes) in ...snip.../application/views/dns/view.php on line 4
�@Error
Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 139817084080128
bytes) in ...snip.../application/views/errors/html/error_php.php on line 9

This is a CodeIgniter app, and line 4 of view.php is a echo of a single quoted string with no
variables at all.

The server config is PHP-FPM with the Ubuntu package from the ondrej PPA
1:7.1+55+ubuntu16.04.1+deb.sury.org+1

It might just be a random glitch, but I certainly found it very surprising.

Test script:
---------------
I'm having a little bit of trouble reproducing the issue, and as the error line is about an
echo I have no clue what test script would cause it.



------------------------------------------------------------------------



--
Edit this bug report at https://bugs.php.net/bug.php?id=75492&edit=1


Thread (5 messages)

« previous php.bugs (#215916) next »