Mike --
You're barking up the wrong tree. There's no reason that Fortran open()
and cloce() statements must be balanced. Many of the files remain in
use as long as jt9 is running; on termination all files are closed be
default.
-- Joe
On 2/21/2018 2:55 PM, Black Michael via wsjt-devel wrote:
Found one more missing close(). All the other opens that aren't in
programs are paired with closes.
In decoder.f90 unit#17 is not closed
if(params%nmode.eq.164)
open(17,file=trim(temp_dir)//'/red.dat', &
status='unknown')
de Mike W9MDB
On Wednesday, February 21, 2018, 1:35:35 PM CST, Black Michael via
wsjt-devel <wsjt-devel@lists.sourceforge.net> wrote:
I wonder if the lack of a close() in readwav.f90 might be responsible?
Looks like there may some others....I see 56 open statements but only 31
closes. Some difference looks correct with multiple open statements in
the logic but sure doesn't look like 25 of them.
de Mike W9MDB
On Wednesday, February 21, 2018, 1:20:54 PM CST, Bill Somerville
<g4...@classdesign.com> wrote:
Hi Doug,
thanks for this analysis. Which WSJT-X mode were you monitoring?
73
Bill
G4WJS.
On 21/02/2018 19:16, Doug Collinge wrote:
This seems to have been swallowed. Apologies if there is a duplication...
---------- Forwarded message ----------
From: *Doug Collinge* <doug.colli...@gmail.com
<mailto:doug.colli...@gmail.com>>
Date: Tue, Feb 20, 2018 at 11:59 AM
Subject:
Memory Leak in jt9 Process
To:
wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
There seems to be a memory leak in the jt9 process started by wsjtx. I
have included a chart showing the memory use growing from about 20MiB
to over 300MiB in the course of 11 hours. I set wsjtx to monitor 40m
overnight and recorded the memory stats produced by /proc/*/statm at
one minute intervals. The change in slope of the curves indicates the
band opening and more signals being decoded.
The configuration here is Ubuntu 17.10 with an RTL-SDR. gqrx
demodulates USB, filters and feeds the audio to wsjt-x 1.9.0-rc1 using
pulseaudio.
Doug VE7GNU
------------------------------------------------------------------------------
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 <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
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 <mailto:wsjt-devel@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
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
------------------------------------------------------------------------------
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
