On 08.05.2013 11:42, Jarod. w wrote:
2013/4/16 Michal Privoznik <mprivozn(a)redhat.com
<mailto:mprivozn@redhat.com>>
On 16.04.2013 11:29, Alex Leonhardt wrote:
> Ah great, thanks!
>
> Alex
In general, it can be a bit difficult to determine the exact commit
which fixes problem you are seeing, because it depends on you concrete
use case. However, you can try running libvirtd with valgrind and see
where libvirtd leaks the most. This as disadvantage of libvirtd running
a bit slower but on the other hand, if it is such huge leak even a
little while should do. Maybe you will discover a new leak :)
I met this issue.thanks
Can you run under valgrind to catch the root cause of the leak?
Or can you update to prove the leak was fixed?
Michal