I discovered an issue with freeing session memory last month and Robert integrated the fix, but we haven't had a 2.5.1 yet so it's still present in your version.
Try replacing your svc.c with this one: https://users.k12system.com/mrwizard/pound/svc-leakfix_unofficial.c And let us know if you have any problems. For that matter, did you try the base64 patch from 2/15 and how did that work for you? Joe > -----Original Message----- > From: (private) HKS [mailto:[email protected]] > Sent: Monday, April 19, 2010 2:29 PM > To: [email protected] > Subject: [Pound Mailing List] Memory leaks in Pound 2.5? > > Since upgrading from 2.4.5 to 2.5, I've noticed Pound gradually > consuming more and more memory until it has to be restarted lest it > consume all my RAM. I've observed this on both OpenBSD 4.6 i386 and > FreeBSD 8 x64. > > For example, an instance that's been around for about a week now is > eating up 154MB. This instance is running a pretty limited > configuration (basically just serving as SSL termination and header > sanitization for a different app) that I've pasted below. There are > only two things I can think of that are even noteworthy: > > - Configuration flag --with-maxbuf384 > - The SSL certificate is a wildcard cert and I'm serving about 2000 > matching subdomains > > Any idea what's going on or what I can look at? > > -HKS > > > > > > User "pound" > Group "pound" > Control "/var/run/pound-se-ctl.socket" > LogFacility daemon > LogLevel 5 > Alive 30 > Client 30 > ConnTO 5 > TimeOut 30 > Grace 30 > > ListenHTTP > Address 10.2.1.83 > Port 80 > RewriteLocation 0 > > HeadRemove "X-Forwarded-For" > AddHeader "X-Forwarded-By: pound" > HeadRemove "X-SSL" > End > > ListenHTTPS > Address 10.2.1.83 > Port 443 > Cert "/usr/local/etc/pound/private/se.pem" > RewriteLocation 0 > > HeadRemove "X-Forwarded-For" > AddHeader "X-Forwarded-By: pound" > HeadRemove "X-SSL" > AddHeader "X-SSL: yes" > End > > Service > Backend > Address 127.0.0.1 > Port 9083 > End > End > > -- > To unsubscribe send an email with subject unsubscribe to > [email protected]. > Please contact [email protected] for questions. -- To unsubscribe send an email with subject unsubscribe to [email protected]. Please contact [email protected] for questions.
