From: Jim Fehlig <jfehlig@novell.com>
To: xen-devel <xen-devel@lists.xensource.com>
Subject: [PATCH] Fix memory leak in xend
Date: Thu, 10 Jul 2008 16:28:50 -0600 [thread overview]
Message-ID: <48768D22.6010005@novell.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 252 bytes --]
We observed OOM kills of xend after ~20 days in openSUSE build service
workers. xend reached around 2.5 G virt, 1.5G res, and 1.8G shared
memory usage. Attached patch provides a plug.
Cheers,
Jim
Signed-off-by: Jim Fehlig <jfehlig@novell.com>
[-- Attachment #2: xend-memleak.patch --]
[-- Type: text/x-patch, Size: 433 bytes --]
diff -r bd97e45e073a tools/python/xen/xend/XendDomainInfo.py
--- a/tools/python/xen/xend/XendDomainInfo.py Tue Jul 08 09:28:50 2008 +0100
+++ b/tools/python/xen/xend/XendDomainInfo.py Thu Jul 10 15:16:57 2008 -0600
@@ -2607,6 +2607,7 @@ class XendDomainInfo:
def _cleanupVm(self):
"""Cleanup VM resources. Idempotent. Nothrow guarantee."""
+ self.metrics.destroy()
self._unwatchVm()
try:
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2008-07-10 22:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 22:28 Jim Fehlig [this message]
2008-08-28 21:52 ` [PATCH] Fix memory leak in xend Stefan de Konink
2008-08-29 1:14 ` Zhigang Wang
2008-08-29 1:42 ` Stefan de Konink
2008-08-29 1:54 ` Zhigang Wang
2008-08-29 1:58 ` Stefan de Konink
2008-08-29 5:28 ` Jim Fehlig
-- strict thread matches above, loose matches on Subject: below --
2007-09-13 4:55 Kouya Shimura
2007-09-10 20:52 [PATCH] Fix 'memory leak' " Jim Fehlig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48768D22.6010005@novell.com \
--to=jfehlig@novell.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.