Bug #52549 [Fbk->Bgs]: No 'M' in memory_limit variable returns 'Could not startup.' Possible mem leak?
Edit report at http://bugs.php.net/bug.php?id=52549&edit=1
ID: 52549
Updated by: felipe@php.net
Reported by: zack_gold at yahoo dot com
Summary: No 'M' in memory_limit variable returns 'Could not
startup.' Possible mem leak?
-Status: Feedback
+Status: Bogus
Type: Bug
Package: PHP options/info functions
Operating System: Linux (Arch Linux)
PHP Version: 5.3.3
Block user comment: N
New Comment:
Thank you for taking the time to write to us, but this is not
a bug. Please double-check the documentation available at
http://www.php.net/manual/ and the instructions on how to
report
a bug at http://bugs.php.net/how-to-report.php
Previous Comments:
------------------------------------------------------------------------
[2010-08-06 17:10:22] zack_gold at yahoo dot com
Oh, interesting.
------------------------------------------------------------------------
[2010-08-06 11:40:23] mike@php.net
It actually is set properly, you set it to 50 bytes, which is too less
to start up.
------------------------------------------------------------------------
[2010-08-06 04:00:32] zack_gold at yahoo dot com
Description:
------------
When you put this into php.ini:
memory_limit = 50;
The output results in:
Could not startup.
There should be a notification to let you know that the memory_limit
isn't set
properly. Maybe it's possible to do memory leaking or something like
that through
this? My knowledge for memory-related stuff is one to none, but maybe
there's a
potential bug here...
Test script:
---------------
Change php.ini memory_limit to "50" like so:
memory_limit = 50;
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/bug.php?id=52549&edit=1
Thread (4 messages)