My suggestion at this point is to take the -exact- "work" code from a block that seems to be causing this memory issue and move it into a test program as a subroutine. Then, from "main" create a replicated set of calls to this "work" and see what happens. The goal here is to remove the GR part of the coding, reducing the code-at-issue to its minimum to show the issue -- or, not show the issue in which case we know it's GR, somehow. - MLD
On Wed, May 15, 2019, at 8:57 AM, Moses Browne Mwakyanjala wrote: > Hello Ben, > In order to test the current hypothesis, I upgraded my system from Ubuntu > 16.04 to 18.04 and GNU Radio from 3.7.11 to 3.7.13.5. > Still, the leak persists. Surprisingly, Michael didn't experience the issue > on his MacOS, running the exact code I'm running at the moment. > I'm not sure what could cause the issue in Ubuntu. > > Regards, > Moses.
_______________________________________________ Discuss-gnuradio mailing list Discuss-gnuradio@gnu.org https://lists.gnu.org/mailman/listinfo/discuss-gnuradio
