We validated that commit 38816336a5 ("node_device_conf: Don't leak
@physical_function in virNodeDeviceGetPCISRIOVCaps") [0] indeed fixes
the leak investigated. Although there are more definitely-lost memory
reports from Valgrind, they are ultimately glibc-related and given the
report was in Trusty
Just a minor update here, we found one leak to be fixed by the following commit:
libvirt.org/git/?p=libvirt.git;a=commit;h=38816336a5 .
We continue the investigation of the other leaks.
Cheers,
Guilherme
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
Hi Christian, thanks for your comment! I didn't receive an email with that
comment, unfortunately.
I'm not sure if they happen on upstream version, I've tried already and saw
different leaks, potentially correlated with the virErr ones.
I couldn't see libxml2 leaks. But i continue the investigat
** Changed in: cloud-archive
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: cloud-archive/mitaka
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: cloud-archive
Status: New => Confirmed
** Changed in: cloud-archive/mitaka
S
Hi,
thanks for the report and your work on it.
Are you sure those issues are not happening on newer versions?
Because
a) if they are fixed in newer versions then I'd ask you to backport the
respective fixes from there (can be partial if they were bigger reworks, but
always better than starting f
** Also affects: cloud-archive
Importance: Undecided
Status: New
** Also affects: cloud-archive/mitaka
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
Leak #2:
==21823==385 (280 direct, 105 indirect) bytes in 1 blocks are definitely
lost in loss record 88 of 106
==21823==at 0x4C2CC70: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==21823==by 0x50A5299: virAlloc (viralloc.c:144)
==21823==by 0x14B185: daemonConf
** Attachment added: "valgrind-definitely_only.txt"
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1844455/+attachment/5289284/+files/valgrind-definitely_only.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs
Leak #3
968 bytes in 1 blocks are definitely lost in loss record 1,313 of 1,405
at 0x4C2AB80: malloc (in /usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
by 0x6D4BA21: xmlGetGlobalState (in /usr/lib/x86_64-linux-gnu/libxml2.so.2.9.3)
by 0x6D4B214: __xmlIndentTreeOutput (in
/usr/lib/x86_64-linu
Leak #1:
==12891==80 bytes in 1 blocks are definitely lost in loss record 949 of
1,360
==12891==at 0x4C2CC70: calloc (in
/usr/lib/valgrind/vgpreload_memcheck-amd64-linux.so)
==12891==by 0x50A5299: virAlloc (viralloc.c:144)
==12891==by 0x50C1C63: virLastErrorObject (virerror.c:240
10 matches
Mail list logo
