Everything

php

Setting memory_limit fails

php.internals

Peter Rendl

22 years ago

Hello all,

I just fetched the latest php5 package for win32 from snaps.php.net
(Built On: Jul 07, 2004 06:30 GMT).

It seems like the ini-setting for memory_limit is ignored and the
default of 8MB is used instead. This also causes installation of PEAR to
fail and probably affects bug #29023.

To reproduce:
php -n -d memory_limit=32M -r "$foo = ini_get('memory_limit');
var_dump($foo);"
string(2) "8M"

I just wanted to clarify that this is not my mistake, before posting a
bug report.


Best regards,
Peter

Edin Kadribasic

22 years ago

Memory limit checking is not compiled in on Windows. So bugs must be caused by
something else.

Edin

On Wednesday 07 July 2004 12:24, Peter Rendl wrote:

Peter Rendl

22 years ago

Edin Kadribasic wrote:

> Memory limit checking is not compiled in on Windows. So bugs must be

caused by

> something else.

Unfortunately phpinfo() does not show compile options for this build.
But http://snaps.php.net/win32/snapshot.log contains this line
"snapshot: forcing memory-limit on". Is it a misinterpretation that this
turns memory limit checking on?

I have an older php version from february available. It returns an empty
string for ini_get('memory_limit') while the current snap gives 8MB.

When installing PEAR I get some errors like this:
Notice: unserialize(): Error at offset 8194 of 8192 bytes in...

-Peter

Andrey Hristov

22 years ago

Peter Rendl wrote:

> Edin Kadribasic wrote:
>  > Memory limit checking is not compiled in on Windows. So bugs must be
> caused by
>  > something else.
>
> Unfortunately phpinfo() does not show compile options for this build.
> But http://snaps.php.net/win32/snapshot.log contains this line
> "snapshot: forcing memory-limit on". Is it a misinterpretation that this
> turns memory limit checking on?
>
> I have an older php version from february available. It returns an empty
> string for ini_get('memory_limit') while the current snap gives 8MB.
>
> When installing PEAR I get some errors like this:
> Notice: unserialize(): Error at offset 8194 of 8192 bytes in...

Oops, is that a new build?

> -Peter
>

andrey

Edin Kadribasic

22 years ago

On Wednesday 07 July 2004 14:21, Peter Rendl wrote:

> Edin Kadribasic wrote:
>  > Memory limit checking is not compiled in on Windows. So bugs must be
>
> caused by
>
>  > something else.
>
> Unfortunately phpinfo() does not show compile options for this build.
> But http://snaps.php.net/win32/snapshot.log contains this line
> "snapshot: forcing memory-limit on". Is it a misinterpretation that this
> turns memory limit checking on?
>
> I have an older php version from february available. It returns an empty
> string for ini_get('memory_limit') while the current snap gives 8MB.

You have uncovered an error in win32 configure script which is fixed now. The
next snap should again have memory limit disabled.

Edin

Peter Rendl

22 years ago

Edin Kadribasic wrote:

> You have uncovered an error in win32 configure script which is fixed now. The
> next snap should again have memory limit disabled.

This is good, thank you.

One more question for my understanding:
Checking the memory limit and setting it, are 2 different things to me.
Why did "php -n -d memory_limit=32M" not set the limit to 32MB?

-Peter