Edit report at http://bugs.php.net/bug.php?id=50480&edit=1
ID: 50480
Comment by: letssurf at gmail dot com
Reported by: lesjno at free dot fr
Summary: memory leak with eval()
Status: Open
Type: Bug
Package: Scripting Engine problem
Operating System: *
PHP Version: 5.3.1
New Comment:
PHP Versions:
-------------
Tested as broken with
5.2.6
5.3.2
Reproduce code:
---------------
<?php
// working code, runs for ever
$code = 'return false;';
while(true) {
$result = eval($code);
$mem = memory_get_peak_usage(true);
var_dump($result, $mem);
}
<?php
// broken code, dies due to memory limit being reached
$code = 'some invalid php code';
while(true) {
$result = eval($code);
$mem = memory_get_peak_usage(true);
var_dump($result, $mem);
}
Expected result:
----------------
A var_dump of false and the peak memory usage, not increasing.
Actual result:
--------------
A var_dump of false and the peak memory usage keeps increasing.
Previous Comments:
------------------------------------------------------------------------
[2010-04-26 10:09:45] lesjno at free dot fr
I've just tried the PHP 5.3.2 release but the memory leak remains.
The test script is the following :
CODE :
------
$status="";
$ch="\$result=true;"; // a chain with a good php syntax
$memory_used1 = memory_get_usage();
$status = @eval($ch) ;
$memory_used2 = memory_get_usage();
echo "chain to eval : \"$ch\" ==> status = ";
var_dump($status);
echo "<BR>";
echo "<b>memory difference =
".($memory_used2-$memory_used1)."<BR><BR></b>\n";
$ch="abcdef"; // a chain with a bad php syntaxe
$memory_used1 = memory_get_usage();
$status = @eval($ch) ;
$memory_used2 = memory_get_usage();
echo "chain to eval : \"$ch\" ==> status = ";
var_dump($status);
echo "<BR>";
echo "<b>memory difference =
".($memory_used2-$memory_used1)."<BR></b>\n";
Actual result:
--------------
chain to eval : "$result=true;" ==> status = NULL
memory difference = 512
chain to eval : "abcdef" ==> status = bool(false)
memory difference = 8632
Expected result:
--------------
chain to eval : "$result=true;" ==> status = NULL
memory difference = 0
chain to eval : "abcdef" ==> status = bool(false)
memory difference = 0
------------------------------------------------------------------------
[2010-04-25 20:39:15] [email protected]
Please try using this snapshot:
http://snaps.php.net/php5.3-latest.tar.gz
For Windows:
http://windows.php.net/snapshots/
------------------------------------------------------------------------
[2009-12-24 01:00:01] php-bugs at lists dot php dot net
No feedback was provided for this bug for over a week, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".
------------------------------------------------------------------------
[2009-12-22 08:59:14] lesjno at free dot fr
Hello jani,
I have a loop to update a database from an excel file. So, for each
excel row I will apply several tests and initializations specified in a
configuration file. The configuration file depend on the user profile.
The eval() function is used, for example, for data initialization : the
configuration file can give a data or a code. For example a specific
date field can take a fix date ("2009-01-01") or can be computed. So,
for example, I can found in a configuration file :
for a user category : $field_init = '2009-01-01' ;
for another user category : $field_init = 'return date("Y-m-d");' ;
I will use the following code :
$data = @eval($field_init) ; if ($data===false) $data=$field_init;
It's only an example but there are a lot of others "eval()" like this
for each excel row treatment.
An excel file can have more than 50000 rows ... so the memory leak is
growing up till the system error ...
------------------------------------------------------------------------
[2009-12-16 12:47:05] [email protected]
Please provide such script that actually has a loop. Simple test
suggested this is just expected and memory does not really grow after
certain point.
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/bug.php?id=50480
--
Edit this bug report at http://bugs.php.net/bug.php?id=50480&edit=1
