I missed the problem. How can I reproduce it?
Thanks. Dmitry.
Lukas Kahwe Smith wrote:
On 17.07.2008, at 03:29, Greg Beaver wrote:
Stanislav Malyshev wrote:
Hi!
zend_destroy_rsrc_list(EG(regular_list)). On the next line,
zend_post_deactivate_modules() is called, which steps through the
On 17.07.2008, at 03:29, Greg Beaver wrote:
Stanislav Malyshev wrote:
Hi!
zend_destroy_rsrc_list(EG(regular_list)). On the next line,
zend_post_deactivate_modules() is called, which steps through the
module
list and unloads all the dynamically loaded modules. If one of
these
dl() is
Hi!
This has nothing to do with dl(). mysqli was loaded in php.ini via
extension=mysqli.so
Oh, I missed that point. Anyway, it sounds logical that all resources
should be freed before modules are unloaded, not the reverse.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED]
Hi,
Does anyone agree that there is an issue to fix here? Messing with the
shutdown order is probably the last thing any RM would like to see
happening ..
regards,
Lukas
On 16.06.2008, at 04:55, Gregory Beaver wrote:
Hi,
I'm getting errors of hashtable already destroyed when running
Stanislav Malyshev wrote:
Hi!
zend_destroy_rsrc_list(EG(regular_list)). On the next line,
zend_post_deactivate_modules() is called, which steps through the module
list and unloads all the dynamically loaded modules. If one of these
dl() is really troublesome...
I think this issue could
Hi,
I'm getting errors of hashtable already destroyed when running
phpMyAdmin with PHP 5.3, and (of course), thinking this is a phar issue,
I've traced through and found a problem in the shutdown order.
Basically, php_request_shutdown() calls zend_deactivate() which calls
