ID: 9223
Updated by: stas
Reported By: [EMAIL PROTECTED]
Old-Status: Closed
Status: Analyzed
Bug Type: Recode related
Assigned To:
Comments:
Better be in 'Analyzed', to know the problem still exists.
Previous Comments:
---
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
On 8 Mar 2001 [EMAIL PROTECTED] wrote:
> ID: 9223
> Updated by: stas
> Reported By: [EMAIL PROTECTED]
> Old-Status: Open
> Status: Closed
> Bug Type: Recode related
> Assigned To:
> Comments:
>
> Seems that this is a recode memory leak, not PHP's. At least
> Insure says that recode library is lea
ID: 9223
Updated by: stas
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Closed
Bug Type: Recode related
Assigned To:
Comments:
Seems that this is a recode memory leak, not PHP's. At least
Insure says that recode library is leaking memory all over
the place. You may want to contact re
