Ron Korving wrote:
> That would be nice. If all memory, even the stuff allocated by functions,
> is freed at the end of the request, I can see where the problem is. It
> would be very useful if this memory really would be freed at the moment
> all references to it disappear. This would be a lot bet
That would be nice. If all memory, even the stuff allocated by functions, is
freed at the end of the request, I can see where the problem is. It would be
very useful if this memory really would be freed at the moment all
references to it disappear. This would be a lot better for the CLI
environment
There was some mail about the memory handling some time ago on
this list..something about making it better in these cases..
Try search the archives for this. (I can't find it right now)
IIRC, there even was a patch..
--Jani
On Thu, 6 Oct 2005, J. Allen Dove wrote:
Unset()
Unset() != free() is the bummer in the CLI env. :-( Def could use that
to help shape the performance contour in a daemon env since the
"request" never ends unless you self-terminate. Even then it can be
tricky to get that lifetime right if your loads change, etc.
-- AD
> "leak", which honestly
On Thu, 6 Oct 2005, J. Allen Dove wrote:
"leak", which honestly surprised me. We even explicitly unset the vars
but that doesn't guarantee the GC kicks off for them near-time?
unset() != free(). The memory allocated is still freed during
the request shutdown (where GC actually kicks in
ay, October 06, 2005 11:58 AM
To: "Ron Korving"
Cc: internals@lists.php.net
Subject: [PHP-DEV] Re: CLI in PHP6
> There was once (can't remember when exactly, so it must be a long time
> ago)
> here on PHP CLI scripts in which it came forward that one should not
rely
There was once (can't remember when exactly, so it must be a long time
ago)
here on PHP CLI scripts in which it came forward that one should not rely
on
such a script to run forever. And it's true; the scripts sometimes
magically
and suddenly die. Now I have no clue where this instability (for
I've had PHP scripts die after weeks or months on Linux without an obvious
reason, and honestly I'm a little bit puzzled on how to debug the situation.
Any suggestions?
Ron
"James Aylett" <[EMAIL PROTECTED]> schreef in bericht
news:[EMAIL PROTECTED]
> On Thu, Oct 06, 2005 at 12:33:16PM +0200, Pe
On Thu, Oct 06, 2005 at 12:33:16PM +0200, Peter Brodersen wrote:
> Jani mentioned in http://bugs.php.net/bug.php?id=34483 : "Running a
> PHP for 24 hours (under windows) is REALLY not supported or suggested.
> It's definately nothing to do with PHP but your OS." (and "Try this on
> a real OS, like
On Thu, 6 Oct 2005 10:48:51 +0200, in php.internals [EMAIL PROTECTED]
("Ron Korving") wrote:
>There was once (can't remember when exactly, so it must be a long time ago)
>here on PHP CLI scripts in which it came forward that one should not rely on
>such a script to run forever. And it's true; the
10 matches
Mail list logo
