SS>> That could also mean that the recode extension does not call SS>> cleanup handlers of the recode library. In the SS>> zlib/ob_gzhandler case that was the primary cause for the SS>> huge memory leak. The problem that it is leaking "in process", i.e. each call to recode_string costs me some memory, allocated inside recode, and not freed even after delete_request. I guess maybe the developers of recode wanted to free it on delete_outer, but that would be strange. Otherwise, recode extension works exactly like written in the recode manual. -- 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]
