Re: [libvirt] Fix memleaks in libvirtd's message processing

2009-09-29 Thread Matthias Bolte
2009/9/29 Daniel P. Berrange : > On Sat, Sep 26, 2009 at 02:24:33AM +0200, Matthias Bolte wrote: >> I tracked down a memleak in libvirtd's message processing. The leak >> was introduced in commit 47cab734995fa9521b1df05d37e9978eedd8d3a2 >> "Split out code for handling incoming method call messages"

Re: [libvirt] Fix memleaks in libvirtd's message processing

2009-09-29 Thread Daniel P. Berrange
On Sat, Sep 26, 2009 at 02:24:33AM +0200, Matthias Bolte wrote: > I tracked down a memleak in libvirtd's message processing. The leak > was introduced in commit 47cab734995fa9521b1df05d37e9978eedd8d3a2 > "Split out code for handling incoming method call messages". This > commit changed the way qemu

[libvirt] Fix memleaks in libvirtd's message processing

2009-09-25 Thread Matthias Bolte
I tracked down a memleak in libvirtd's message processing. The leak was introduced in commit 47cab734995fa9521b1df05d37e9978eedd8d3a2 "Split out code for handling incoming method call messages". This commit changed the way qemud_client_message objects were reused. Before this commit: - qemudWorke