[ovs-discuss] ovs-vswitchd memory consumption behavior
blp at ovn.org
Wed Mar 6 00:08:44 UTC 2019
>From the core dump (that you sent me off-list), it looks like you are
using MUSL libc, rather than glibc:
blp at sigill:~/nicira/ovs/_build(127)$ ldd ./ovs-vswitchd
libssl.so.1.1 => /lib/x86_64-linux-gnu/libssl.so.1.1 (0x00007f6bc4526000)
libcrypto.so.1.1 => /lib/x86_64-linux-gnu/libcrypto.so.1.1 (0x00007f6bc423e000)
libcap-ng.so.0 => /lib/x86_64-linux-gnu/libcap-ng.so.0 (0x00007f6bc4236000)
libc.musl-x86_64.so.1 => not found
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f6bc4231000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f6bc4210000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f6bc404d000)
/lib/ld-musl-x86_64.so.1 => /lib64/ld-linux-x86-64.so.2 (0x00007f6bc47fb000)
blp at sigill:~/nicira/ovs/_build(0)$
Is that correct?
On Tue, Mar 05, 2019 at 03:08:59PM -0800, Ben Pfaff wrote:
> That is worth a shot. Thank you.
> On Tue, Mar 05, 2019 at 11:06:08PM +0000, Fernando Casas Schössow wrote:
> > Too bad. :(
> > Should I start over but leave it running for let's say 5-7 days instead?
> > Maybe 48 hours was not enough.
> > On mié, mar 6, 2019 at 12:03 AM, Ben Pfaff <blp at ovn.org> wrote:
> > On Tue, Mar 05, 2019 at 09:56:30PM +0000, Fernando Casas Schössow wrote:
> > Please find attached valgrind log. It was running for around 48 hours. Hopefully it was enough otherwise let me know and I can run it again for more time.
> > Thanks for the log. There are several suspicious warnings to look at in this log, and I will do that. But it does not point out any significant memory leaks--even if I consider all of the "possible leaks" it mentions as actual leaks (usually, they are not), they are much too small by orders of magnitudes to be the problem reported.
More information about the discuss