Re: [Speedycgi-users] Memory leak in speedy_backend
Brought to you by:
samh
Menu
▾
▴
Re: [Speedycgi-users] Memory leak in speedy_backend
|
From: James H. T. <jh...@la...> - 2003-10-06 17:24:05
|
Thats great news! Thanks much for creating and maintaining this program. Jim James H. Thompson jh...@la... ----- Original Message ----- From: "Sam Horrocks" <sa...@da...> To: "James H. Thompson" <jh...@la...> Cc: <spe...@li...> Sent: Sunday, October 05, 2003 8:47 PM Subject: Re: [Speedycgi-users] Memory leak in speedy_backend > THanks for the bug report and the patch. There's new code on the cvs > server to fix this. > > The patch you submitted reduced the leak quite a bit, but it didn't > go away altogether. I couldn't get eval_sv to work without leaking, so > I replaced it with a call_sv which seems to work. > > > > > This is a multi-part message in MIME format. > > > > ------=_NextPart_000_0047_01C37B19.2DEAB060 > > Content-Type: text/plain; > > charset="Windows-1252" > > Content-Transfer-Encoding: quoted-printable > > > > I'm using SpeedyCGI in a high volume application on Redhat 8, and = > > noticed that the memory usage of speedy_backend continually grew over = > > time, even if the -r option was set to low number like 3. > > > > The memory consumption seemed to be tied to speedy_backend creating a = > > new child. > > > > I created an experimental patch to fix this. > > > > The patch is here: > > www.voip-info.org/speedycgi > > > > > > Jim > > > > James H. Thompson > > jh...@la... > > > > ------=_NextPart_000_0047_01C37B19.2DEAB060 > > Content-Type: text/html; > > charset="Windows-1252" > > Content-Transfer-Encoding: quoted-printable > > > > <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> > > <HTML><HEAD> > > <META http-equiv=3DContent-Type content=3D"text/html; = > > charset=3Dwindows-1252"> > > <META content=3D"MSHTML 6.00.2800.1126" name=3DGENERATOR> > > <STYLE></STYLE> > > </HEAD> > > <BODY bgColor=3D#ffffff> > > <DIV><FONT size=3D2>I'm using SpeedyCGI in a high volume application on = > > Redhat 8,=20 > > and noticed that the memory usage of speedy_backend continually grew = > > over time,=20 > > even if the -r option was set to low number like 3.</FONT></DIV> > > <DIV><FONT size=3D2></FONT> </DIV> > > <DIV><FONT size=3D2>The memory consumption seemed to be tied=20 > > to speedy_backend creating a new child.</FONT></DIV> > > <DIV><FONT size=3D2></FONT> </DIV> > > <DIV><FONT size=3D2>I created an experimental patch to fix = > > this.</FONT></DIV> > > <DIV><FONT size=3D2></FONT> </DIV> > > <DIV><FONT size=3D2>The patch is here:</FONT></DIV> > > <DIV><FONT size=3D2> <A=20 > > href=3D"http://www.voip-info.org/speedycgi">www.voip-info.org/speedycgi</= > > A></FONT></DIV> > > <DIV> </DIV> > > <DIV><FONT size=3D2></FONT> </DIV> > > <DIV><FONT size=3D2>Jim</FONT></DIV> > > <DIV> </DIV> > > <DIV><FONT size=3D2>James H. Thompson<BR><A=20 > > href=3D"mailto:jh...@la...">jh...@la...</A><BR></FONT></DIV></BODY></HT= > > ML> > > > > ------=_NextPart_000_0047_01C37B19.2DEAB060-- > > > > > > > > ------------------------------------------------------- > > This sf.net email is sponsored by:ThinkGeek > > Welcome to geek heaven. > > http://thinkgeek.com/sf > > _______________________________________________ > > Speedycgi-users mailing list > > Spe...@li... > > https://lists.sourceforge.net/lists/listinfo/speedycgi-users > |
