Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:451
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <006d01c2f5de$d5d42470$06dea8c0@cyberware.local>
To: "php-dev" <internals@lists.php.net>
References: <1048001497.1516.3.camel@localhost.localdomain> <001901c2ed6f$b3be6f70$0301a8c0@TRABAJOS2> <016701c2f156$f6d83080$06dea8c0@cyberware.local> <Pine.LNX.4.53.0303231809291.5087@zaneeb.brainnet.i>
Date: Sat, 29 Mar 2003 05:34:53 -0500
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
Subject: ZE1 module shutdown
From: rrichards@digarc.com ("Rob Richards")

I am getting some serious memory leaks due to the difference between a
module loaded via the ini file and one loaded via a dl call in a script.

When loaded via the ini file, the memory is fine as the resources are killed
in the correct order via the zend_hash_graceful_reverse_destroy call.

When a module is loaded via dl call, the module is removed via the
modules_destructor which kills off the resources in the order they were
created in a script (at least looking at the stack while debugging this is
what it shows is happening).

Is this behavior by design or is it incorrect as some extensions rely on the
reverse destruction on the resources. I would assume this is incorrect as it
now no longer consistent execution of an extension if one were to load the
extension using dl rather than from the ini file.
Running some of them under Windows, php completely dies due to memory access
violations.

Thanks,

Rob