> > My experience with trying to clear the change track and re-establish it > > leads > > to history being lost [this is likely from my not fully understanding what > > happens with sequence numbers over turning tracking on and off] and so it > > is > > more efficient to just leave change tracking on. Under this scenario, I'm > > pretty convinced that this code would amount to a memory leak. > > > > Could you provide more exact description of the problem and the steps/code to > reproduce.
I ran valgrind on idl test cases with this change and they all came out clean: make check-valgrind TESTSUITEFLAGS='-k idl' find . -name "valgrind.*" | xargs cat _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
