php-developer-list | 2001122
Date: 12/21/01
- Next message: Zeev Suraski: "Re: [PHP-DEV] SAPI Module Leaking"
- Previous message: Zeev Suraski: "Re: [PHP-DEV] SAPI Module Leaking"
- In reply to: Zeev Suraski: "Re: [PHP-DEV] SAPI Module Leaking"
- Next in thread: Zeev Suraski: "Re: [PHP-DEV] SAPI Module Leaking"
- Reply: Zeev Suraski: "Re: [PHP-DEV] SAPI Module Leaking"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
It sounds like there was a particular reason for writing it this way ?
I am considering what effect it will have on me if I simply require that
people use thread pooling, and I'm going to do some tests to see whether
there's still a leak condition or if it stabilizes when I reuse them.
Alex
On 12/21/01 4:20 PM, "Zeev Suraski" <zeev <email protected>> wrote:
> Well, it is pretty complicated to fix, even though it's been a very long
> while since I touched this code so I may be wrong. As far as I recall, the
> TSRM hash tables won't reuse entries that were freed by threads that
> terminated. Fixing this, especially without hurting performance, may be
> quite complicated.
>
> That said - I'm not sure it accounts for 1KB per request. There could be
> leaks in other places.
-- PHP Development Mailing List <http://www.php.net/> To unsubscribe, e-mail: php-dev-unsubscribe <email protected> For additional commands, e-mail: php-dev-help <email protected> To contact the list administrators, e-mail: php-list-admin <email protected>
- Next message: Zeev Suraski: "Re: [PHP-DEV] SAPI Module Leaking"
- Previous message: Zeev Suraski: "Re: [PHP-DEV] SAPI Module Leaking"
- In reply to: Zeev Suraski: "Re: [PHP-DEV] SAPI Module Leaking"
- Next in thread: Zeev Suraski: "Re: [PHP-DEV] SAPI Module Leaking"
- Reply: Zeev Suraski: "Re: [PHP-DEV] SAPI Module Leaking"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

