[Xen-bugs] [Bug 1507] New: memory leak in pyxc_physinfo in xc.c

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1507

           Summary: memory leak in pyxc_physinfo in xc.c
           Product: Xen
           Version: unstable
          Platform: All
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Tools
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: kingram@xxxxxxxxx


When physinfo() is called it returns a dictionary containing information about
the host server. 

Two new items have been added to the dictionary since Xen 3.0.3, "node_to_cpu"
and "node_to_memory". I think there is something wrong with the way these are
created - something to do with the reference counting, I'm not sure what - but
every call to physinfo leaves a copy of these two objects on the heap that
don't get garbage collected.

So if I use gc.get_objects() before and after calls to physinfo I can see these
two objects per call and they don't go away when the dictionary returned by the
function is gone and the garbage collector has been called.

We have seen this problem because we are using libvirt to monitor our system.
We get the domains through libvirt, every few seconds.  This causes physinfo to
be called (from XendNode.py), so we see the xend memory constantly increasing.

Using gc.get_objects I was able to track the problem down to physinfo and that
the leaked objects were the "node_to_cpu" and "node_to_memory" lists.

To reproduce the problem, run "xm info" continuously (it calls physinfo). With
one VM, xend memory increases at about 1 meg every 3 or 4 minutes. The leak
size is proportional to the number of VMs because the objects being leaked are
per VM.


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

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