I don't see a memory leak -- but do see a large chunk of memory being
used...over 400MB by both 32-bit and 64-bit Windows versions. Others have
mentioned this too.
330MB of that is the main wsjtx.exe program and not the DLLs.
I was able to compile a debug version and put a break point in
Hi Björn,
I have not been able to reproduce anything like the behavior you
describe. For one example, I started WSJT-X in FT8 mode, monitoring a
fairly busy 15 m band. Memory usage reported by Windows TaskManager
over the first ~5 hours looks like this:
UTC Memory
--
1930
Greetings; can you describe what mode you are using? If you left it going for a
few days without deciding any signals (e.g. with no antenna) same behavior?
What radio and interface to the radio? Any other information you could share
would be most appreciated.
Thanks!
-Brian N9ADG
Sent via
My RAM (8 Gbyte) fills up if I let rc1 run for a few days. It does not
happen with 2.6.1.
Interestingly enough the task manager does not show WSJT-X to be the
culprit but when
I stop it, up to 5Gbyte are freed up.
Also, sometimes rc1 allocates 630Mbyte of RAM when started. Other times
90Mbyte.
Hi Uwe,
Just an FYI, in general settings, if the checkbox "Calling CQ forces Call 1st"
is checked, then even if you select CQ: NONE in the dropdown box on the main
window, it will switch to CQ: First as soon call CQ This behavior 270 rc1 is
the same as it was in 261. If you select CQ: Max
I normally operate WSPR with band-hopping enabled. Today I turned it off
for testing.
Fedora Core 38, 64-bit, built from source, to Yaesu FT-950 via Signalink
USB.
With band-hopping off, the "Enable TX" button stays enabled during multiple
receive cycles and even after a scheduled transmit cycle.
