:28 am
Subject: Re: [wsjt-devel] Memory leak in 2.7.0 rc1?
Quick test on a W10 Intel laptop with no rig connected shows 94MB used.
Alan G0TLK On 26/05/2023 14:22, Fred Price via wsjt-devel wrote:
I started 2.7.0-rc1 Windows 11 Ryzen 5 task manager shows 473mb for WSJT.exe.
I then closed 2.7.0
Quick test on a W10 Intel laptop with no rig connected shows 94MB used.
Alan G0TLK
On 26/05/2023 14:22, Fred Price via wsjt-devel wrote:
I started 2.7.0-rc1 Windows 11 Ryzen 5 task manager shows 473mb for WSJT.exe.
I then closed 2.7.0-Tx1 and opened 2.6.1 task manger shows 147mb for WSJT.exe.
Once when using a microsoft C compiler
in windows 7 a memory leak appeared..
The person i was working with blamed it
on the fact that i was using pointers.
BUT
Once we reduced down to the minimum
code that produced the leak it contained no
pointers.
It was caused by only that compiler.
It was
Turns out Task Manager shows different memory usage then the System Informer I
use and also Process Explorer.
System Informer says 444MB but Task Manager says 44MB on a clean config (no rig
selected or anything done).
Process Explorer shows 450MB.
So I don't believe Task Manager is correct at
Around 125 MB, consistent with changing configurations (separate configs
for each mode).
FT8, MSK144, FT8,...all around 125 MB starting. Q65 127 MB after about 2
hours of operation, so it is essentially the same.
We checked with our zoom group, we are all running WSJT-X 2.7.0 RC1
Improved Plus by
2.6.1 gives me the same 450MB on a clean AppData\Local\WJST-X setup.
Mike W9MDB
On Friday, May 26, 2023 at 08:30:02 AM CDT, Fred Price via wsjt-devel
wrote:
I started 2.7.0-rc1 Windows 11 Ryzen 5 task manager shows 473mb for WSJT.exe.
I then closed 2.7.0-Tx1 and opened 2.6.1 task
I started 2.7.0-rc1 Windows 11 Ryzen 5 task manager shows 473mb for WSJT.exe.
I then closed 2.7.0-Tx1 and opened 2.6.1 task manger shows 147mb for WSJT.exe.
Both were opened on a pretty quiet 6M band.
I let 2.7.0-rc1 run for around 4 hours this morning with no memory leaks. My
settings for
What save options are selected in these high mem use cases?
BCNU DE N2LO~>
> On 05/25/2023 11:42 PM EDT Black Michael via wsjt-devel
> wrote:
>
>
> 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
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.
12 matches
Mail list logo