On 27/02/2018 22:09, Black Michael via wsjt-devel wrote:
This patch solves at least part of the memory leak problem seen with
jt9.exe running under WSJT-X control. jt9 happily passes valgrind
checks running standalone. It's the looping of jt9a causing problems.
In Windows you'll now see the memory usage go up and down whereas
before it would only go up.
https://www.dropbox.com/s/mhnqzepw1fvbtt3/jt9a.patch?dl=1
<https://www.dropbox.com/s/mhnqzepw1fvbtt3/jt9a.patch?dl=0>
HI Mike,
that change is de-optimizing the FFT plan caching and should not be
needed. The creation of FFTW3 processing plans is an expensive step and
they are carefully preserved across decoding passes for good reason. Any
memory accumulated is not a leak as the plans created will surely be
reused in later decoding passes.
I am surprised that valgrind is identifying leaks for FFT plans, can you
share a leak report showing that please?
73
Bill
G4WJS.
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
