From: Stefan Weil <sw@weilnetz.de>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] full valrind report
Date: Wed, 29 Feb 2012 18:29:08 +0100 [thread overview]
Message-ID: <4F4E6064.1060608@weilnetz.de> (raw)
In-Reply-To: <20120229161927.GC8661@redhat.com>
Am 29.02.2012 17:19, schrieb Michael S. Tsirkin:
> Here's a full report of possible leaks:
> Any idea? I am invedtigating.
Hi Michael,
try valgrind with --track-origins=yes. It costs some memory, but
improves diagnostics not only for memory leaks.
Most important are the leaks marked with "definitely lost".
A lot of them are just missing destructors when QEMU terminates.
Some QEMU classes provide an init function, but no exit function,
for example. If you suspect a leak, you can try to re-run QEMU
and look whether it is possible to increase the leak: repeat an
action in the QEMU monitor several times, connect to the VNC
server more than once, let the emulation run for a long time
and so on. This kind of leaks is dangerous for long running
QEMU instances or allows denial of service attacks.
Good (bug) hunting!
Stefan W.
prev parent reply other threads:[~2012-02-29 17:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 16:19 [Qemu-devel] full valrind report Michael S. Tsirkin
2012-02-29 17:29 ` Stefan Weil [this message]
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=4F4E6064.1060608@weilnetz.de \
--to=sw@weilnetz.de \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
/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.