WF>> Ahhh.
WF>>
WF>> It may sound like a stupid question, but why not?
Because reference-counting mechanisms of memory management are not fit to
deal with circular references.
WF>> And is it likely to in the future?
I won't be holding my breath for it. That's the basic property of
reference-counting, so it's not easy to make it behave differently.
Anyway, unless you have very-long-running very-memory-greedy scripts,
these leaks shouldn't bother you - Zend memory manager cleans them up on
every request.
WF>> As for the leaks, when on a production system (--disable-debug)
WF>> does PHP catch and free them after each request (provided they
WF>> are emalloc'd) ?
Yes. You don't see the messages, but the memory manager is still there :)
--
Stanislav Malyshev, Zend Products Engineer
[EMAIL PROTECTED] http://www.zend.com/ +972-3-6139665 ext.115
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To contact the list administrators, e-mail: [EMAIL PROTECTED]
