ID: 10204
User Update by: [EMAIL PROTECTED]
Old-Status: Feedback
Status: Open
Bug Type: Sockets related
Description: fgets causes memory leaks
> I am in the process of working on a file abstraction for this stuff, so it will be
>rewritten.
Hmm. I'm already using an abstraction layer; Net_Soc
ID: 10204
Updated by: wez
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Feedback
Bug Type: Sockets related
Assigned To:
Comments:
Sorry - I somehow missed the unset.
However, unset just removes the variable from the symbol table - try using $page =
null instead.
I am in the proc
ID: 10204
User Update by: [EMAIL PROTECTED]
Status: Open
Bug Type: Sockets related
Description: fgets causes memory leaks
> Um, yes, the memory usage increases because you are appending an infinite number of
>copies
of the google page to your $page variable.
No, that's what the unset is for.
ID: 10204
User Update by: [EMAIL PROTECTED]
Old-Status: Feedback
Status: Open
Bug Type: Sockets related
Description: fgets causes memory leaks
> Um, yes, the memory usage increases because you are appending an infinite number of
>copies
of the google page to your $page variable.
No, that's w
ID: 10204
Updated by: wez
Reported By: [EMAIL PROTECTED]
Old-Status: Open
Status: Feedback
Bug Type: Sockets related
Assigned To:
Comments:
Um, yes, the memory usage increases because you are appending an infinite number of
copies of the google page to your $page variable.
I can't see any le
ID: 10204
Updated by: wez
Reported By: [EMAIL PROTECTED]
Status: Open
Bug Type: Sockets related
Assigned To:
Comments:
I noticed this last night in the socket code: it uses a simple read-buffering scheme
where the read buffer will only grow, so we are effectively storing the everything we
have