[Varnish] #538: [varnish-2.0.4] Potential Memory Leak

Varnish varnish-bugs at projects.linpro.no
Thu Nov 12 10:04:32 CET 2009

#538: [varnish-2.0.4] Potential Memory Leak
 Reporter:  pprocacci          |        Owner:  phk    
     Type:  defect             |       Status:  closed 
 Priority:  high               |    Milestone:         
Component:  varnishd           |      Version:  trunk  
 Severity:  major              |   Resolution:  invalid
 Keywords:  Memory Leak 2.0.4  |  
Changes (by tfheen):

  * status:  new => closed
  * resolution:  => invalid


 Replying to [comment:10 kb]:
 > Your pmap shows that varnish is correctly allocating the 300MB you
 specified.  The rest of the RAM is spent on the compiled config (always
 about 80MB in my experience) and 10MB of preallocated stack per worker
 thread.  10MB is apparently your distribution's default stacksize (see
 'ulimit -a' or 'limit').

 The 80MB is the log file that is mmap-ed into the memory space, not the
 configuration.  The configuration looks like:

 00007ff4cda31000     16K r-x--  /tmp/_v1/vcl.1P9zoqAU.so
 00007ff4cda35000   2044K -----  /tmp/_v1/vcl.1P9zoqAU.so
 00007ff4cdc34000      4K rw---  /tmp/_v1/vcl.1P9zoqAU.so

 I wouldn't worry about the RSS, it's irrelevant and is just a small
 overhead for the kernel to keep track of some extra pages.  The only
 exception is if you're on a 32 bit platform.

 I'll close this bug as I believe kb has shown quite well where the memory
 is going and we don't have any unaccounted for.

Ticket URL: <http://varnish.projects.linpro.no/ticket/538#comment:12>
Varnish <http://varnish.projects.linpro.no/>
The Varnish HTTP Accelerator

More information about the varnish-bugs mailing list