I'm not sure that you are looking at the right place to solve the
problem. If the leaks are in phpinfo (or in memory allocated by php),
then maybe (really not sure).
But if the leaks are in IM as their extension does not use php memory
manage, it is not something fixable by php or anything else but IM.
Pierre you are getting me totally wrong.
I dont really care for this particular ImageMagick(Wand) or even phpinfo
leak at all :)
What I am talking about is a feature which similar as 'memory_limit' (inside
one script runtime) limits maximum memory usage for a long running php child
(if spawned with the -b option (external FASTCGI Server mode)).
At the moment the only option to avoid memory leaks is to set
PHP_FCGI_MAX_REQUESTS after which the child dies and a new is spawned. Still
the memory usage can grow (as example in this case) way too quick to
actually hit the request limit, which may bring the system in OOM state.
The patch was provided for 4.x branch
http://www.zend.com/zend/week/pat/pat48.txt
So I wanted to get some feebacks (without filling the feature request at
bugs.php.net which I apologise for) if its something worth to implement.
Probably to hear something from Dmitry.
Keep an eye on the current 2.1.0 development, it will be really fast :)
Is the source allready available for testing?
Those 3 remaining tasks in roadmap didnt look problematic at this state
(though I suppose there are more issues)..
rr
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
