public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Ken Brown <kbrown@cornell.edu>
To: km2z7kca0oge@opayq.com, cygwin@cygwin.com
Subject: Re: Cygwin PHP (all available versions) has a hard 4MB memory limit
Date: Sat, 18 Jul 2020 22:11:01 -0400	[thread overview]
Message-ID: <0077be8f-2c24-68c3-c6ea-f6ece6b7b0cf@cornell.edu> (raw)
In-Reply-To: <1869633229.76476.1595021996652@smtp4.opayq.com>

On 7/17/2020 5:39 PM, km2z7kca0oge--- via Cygwin wrote:
> Hi there,
> 
> Recently I've noticed that PHP seems have to hard 4MB memory limit,

[...]

> Example script:
> ```
> <?php
> 
> echo ini_get('memory_limit'), "\n";
> 
> file_get_contents('http://mirror.cwcs.co.uk/centos/8.2.2004/isos/x86_64/CentOS-8.2.2004-x86_64-dvd1.iso'); // A large file such as an ISO.
> ```
> 
> Output:
> $ php test.php
> 128M
> PHP Fatal error:  Out of memory (allocated 4194304) (tried to allocate 2097184 bytes) in /c/Users/JackBlower/tmp-safe/test.php on line 5

Thanks for the simple reproduction steps.  I've run this under gdb, and the 
function zend_mm_alloc_huge, which tries to get a chunk of memory from the 
system, seems to be failing when it tries to increase the zend heap from 4MB to 
6MB.  I'm in the process of building an unoptimized version of php to make 
debugging easier, in the hope of figuring out why the function is failing.

Ken

  parent reply	other threads:[~2020-07-19  2:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 21:39 km2z7kca0oge
2020-07-17 22:39 ` Brian Inglis
2020-07-18  7:29 ` Andrey Repin
2020-07-19  2:11 ` Ken Brown [this message]
2020-07-21 20:45   ` Ken Brown
2020-08-04  1:57     ` Cary Lewis
2020-08-04 10:45       ` Ken Brown
2020-08-04 13:35         ` Cary Lewis
2020-08-04 13:58           ` Ken Brown
2020-07-18 15:33 km2z7kca0oge
2020-07-18 17:32 ` Brian Inglis
2020-07-18 15:54 km2z7kca0oge
2020-07-21 20:58 km2z7kca0oge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0077be8f-2c24-68c3-c6ea-f6ece6b7b0cf@cornell.edu \
    --to=kbrown@cornell.edu \
    --cc=cygwin@cygwin.com \
    --cc=km2z7kca0oge@opayq.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).