Re: [ovs-dev] [ovn] Memory leak in ovn-northd: which fix is preferred?

On Wed, Aug 17, 2022 at 12:58 AM Ales Musil wrote: > > On Tue, Aug 16, 2022 at 1:50 PM Olaf Seibert via dev < > ovs-dev@openvswitch.org> wrote: > > > Hi! We discovered a memory leak in ovn-northd, which grows quickly, caused > > by > > commit 7b56f69580e1f390d9c6753a2cb8f0dbfbb4c467 (dated Wed

Re: [ovs-dev] [ovn] Memory leak in ovn-northd: which fix is preferred?

On Tue, Aug 16, 2022 at 1:50 PM Olaf Seibert via dev < ovs-dev@openvswitch.org> wrote: > Hi! We discovered a memory leak in ovn-northd, which grows quickly, caused > by > commit 7b56f69580e1f390d9c6753a2cb8f0dbfbb4c467 (dated Wed Feb 23 09:30:00 > 2022 > +). We also found a fix for it. I am

[ovs-dev] [ovn] Memory leak in ovn-northd: which fix is preferred?

Hi! We discovered a memory leak in ovn-northd, which grows quickly, caused by commit 7b56f69580e1f390d9c6753a2cb8f0dbfbb4c467 (dated Wed Feb 23 09:30:00 2022 +). We also found a fix for it. I am however not familiar with this code, so when I looked a bit further, I wondered if a different

[ovs-dev] [ovn] Memory leak in ovn-northd: which fix is preferred?

Hi! We discovered a memory leak in ovn-northd, which grows quickly, caused by commit 7b56f69580e1f390d9c6753a2cb8f0dbfbb4c467 (dated Wed Feb 23 09:30:00 2022 +). We also found a fix for it. I am however not familiar with this code, so when I looked a bit further, I wondered if a different