At 10:03 AM 1/14/2004 -0500, Sterling Hughes wrote:
> Looks like a circular reference to me. It's supposed to leak :)
>
Yep - but shouldn't object destruction be forced before the memory
manager cleans it up. The example could rather be put as:
function __construct() {
$th
> Looks like a circular reference to me. It's supposed to leak :)
>
Yep - but shouldn't object destruction be forced before the memory
manager cleans it up. The example could rather be put as:
value = new GenericObject($this);
}
function __destruct() {
print "Cal
Andi Gutmans ([EMAIL PROTECTED]) schrieb:
>
> These are not *real* memory leaks because they are cleaned up at the end of
> the request.
>
Hi Andy,
thanks a lot for making this clear.
Thats why I told that I'm not sure if I understand this right ;-).
Thomas
--
PHP Internals - PHP Runtime De
At 10:29 AM 1/14/2004 +0100, Thomas Seifert wrote:
Andi Gutmans wrote:
Looks like a circular reference to me. It's supposed to leak :)
Andi
Hi Andy,
not sure if I understood this right but thats supposed to be that way?
Anyone CAN create memory-leaks in php if he just wants?
I'm not sure if hoster
Andi Gutmans wrote:
Looks like a circular reference to me. It's supposed to leak :)
Andi
Hi Andy,
not sure if I understood this right but thats supposed to be that way?
Anyone CAN create memory-leaks in php if he just wants?
I'm not sure if hosters will like that behaviour with their
apache proc
Looks like a circular reference to me. It's supposed to leak :)
Andi
At 06:42 PM 1/13/2004 -0500, Sterling Hughes wrote:
Hey,
The attached script gives 10 leaks when PHP5 is compiled with
--enable-debug. These problems are also related to Bug #26765, I'll be
taking a look at it, unless someone
Hey,
The attached script gives 10 leaks when PHP5 is compiled with
--enable-debug. These problems are also related to Bug #26765, I'll be
taking a look at it, unless someone knows the cause already.
The leaks caused when running it are:
/home/sterling/work/php/php-src/Zend/zend_execute.c(2840)
