[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-devel] [BUG] memory leak in xend


  • To: "Christopher S. Aker" <caker@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
  • Date: Tue, 5 Apr 2005 07:49:24 +0100
  • Delivery-date: Tue, 05 Apr 2005 06:52:08 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcU5n4wSEA3JXCViTNKN/3UgKtD7dAAC9h3g
  • Thread-topic: [Xen-devel] [BUG] memory leak in xend

 > > My xend process is currently at 462M.  To reproduce: start 
> a domain, 
> > telnet/xencons into the console, make some output (find / is a good 
> > way) and watch xend's memory rise.
> 
> Ok, it's not console output.  xend's memory flickers up/down, 
> but ends on the same number.
> 
> I'm trying "watch -n0 xm list" now. So far, it's gone up 700k 
> in the last minute.  It appears as though every run through 
> "xm list" list adds ~2k

Since pyhthon is a garbage collected language, this is not unexpected.
It will reclaim the memory only ehen the GC runs.

You can probably set tuning parameters for python's GC if you want to
reclaim the memory earlier. See python.org.

Ian

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.