Re: PHP allocating too much memory
| From: | Michael Felt | Date: | Wed, 15 Jun 2016 15:34:39 +0000 |
| Subject: | Re: PHP allocating too much memory | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-94014@lists.php.net to get a copy of this message | ||
On 15-Jun-16 15:55, Rowan Collins wrote:
On 15/06/2016 14:01, Peter LeBrun wrote:FYI: I have seen similar issues with mixed environments (32 and 64-bit) - at this point I am surprised that you can even dlopen() both sizes (my OS now refuses to dlopen() 32-bit modules aka shared libraries when 64-bit application and v.v.)The weirdest part about this is that PHP is somehow trying to allocate 140TB of memory.I've seen numbers like that a few times - always around 140TB, but the exact number varies. I assume it's an overflow (or underflow?) somewhere, but the exact mechanism escapes me. (It's close to 2^47, but not very close; I've got examples logged as "low" as 140090229815192, and I think I've seen under 140 trillion.) In hex: 00007F694C627798 - so apparently 00007F69400000000 is common to all.
Apart from sheer curiosity of where this magic number comes from, I wonder if there is some sanity check missing in the memory manager to at least display a different error message... Regards,