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.
