hi,
> 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.
i have hit on this issue while trying to make a sapi module. my problem was
that memory emalloc-ed _before_ the request got efree-ed by the memory
manager after the request and when i efree it afterwards a total memory mess
occurs (sigsegv, infinite loop in libc free or something more nasty)...
is there more info on exactly where emalloc tracks memory and when frees all
unfreed blocks in the process of
sapi_startup
php_module_startup
// memory alloced here gets freed by request_shutdown (i suppose)
php_request_startup
php_execute_script
php_request_shutdown
php_module_shutdown
sapi_shutdown
or i am missing something important?
b.
--
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]
