Can your machine's memory be upgraded to 32G or 64G?
Apparently you are suffering from memory fragmentation that can probably be
cured with more memory.
Mike
On Tuesday, October 20, 2020, 05:13:55 PM CDT, Bill Barrett
wrote:
Found some errors in the event viewer:Windows successfully
Found some errors in the event viewer:
Windows successfully diagnosed a low virtual memory condition.
The following programs consumed the most virtual memory:
SmartSDR.exe (1004) consumed 1,531,441,152 bytes,
LogOMUI.exe (4628) consumed 347193344 bytes, and
PowerGeniusDesktop.exe (27412) consumed 3
Hello Mike-
The crash usually takes about a week of continuous running of Flex SSDR and
6-8 instances of WSJT-X.
On Tue, Oct 20, 2020 at 1:30 PM Black Michael wrote:
> Question is what happens after several days of running.
>
> The subprocess error indicates it's jt9.exe not being satisfied.
>
Question is what happens after several days of running.
The subprocess error indicates it's jt9.exe not being satisfied.
So maybe jt9.exe is asking for a fairly big block of memory somewhere and
that's what is failing?
Looks like downsamp9.f90 tries to allocate a real of 653184 which ends up being
This article also gives a full explanation - updated in 2019.
https://techcommunity.microsoft.com/t5/ask-the-performance-team/the-basics-of-page-faults/ba-p/373120
Alan G0TLK
On 20/10/2020 15:23, Black Michael via wsjt-devel wrote:
Hmmm...not what this says...they claim a hard fault is asking f
Not seeing any Hard Faults/sec in the resource manager.
LatencyMon shows hard faults mostly for Flex SSDR and a few for WSJT-X and
JT9.
Flex software is running around 1.3 gig.
Bill W2PKY
On Tue, Oct 20, 2020 at 9:49 AM Black Michael via wsjt-devel <
wsjt-devel@lists.sourceforge.net> wrote:
Hmmm...not what this says...they claim a hard fault is asking for virtual
memory (i.e. swap).
https://answers.microsoft.com/en-us/windows/forum/windows_vista-performance/i-see-alot-of-hard-faults-per-second-should-i-do/68bcc824-7a2c-4231-9a36-bc4ce123af0b
Mike
On Tuesday, October 20, 202
Hello Mike-
Currently Windows is managing the swap file which is 25Gig.
Can't find the file but my memory looks a lot like yours. Have 808mb free
memory, 8gigs standby 7 in use.
Have been keeping the task manager open to see if I can spot a process
using excessive memory but never see anything susp
On 20/10/2020 14:51, Bill Somerville wrote:
On 20/10/2020 14:44, Black Michael via wsjt-devel wrote:
Any hard faults means you're using swap space.
Mike,
that's incorrect information, the most common cause of hard page
faults is where a process requires more memory. A hard page fault is a
r
Mike I went through it with band change on rig and returned to see
unique settings such as IPO state restored as set there previous. That
is all good.
wsjtx band change will maintain same IPO setting from previous band
regardless of prior saved setting on destination band..
73
Adrian Fews
On 20/10/2020 14:44, Black Michael via wsjt-devel wrote:
Any hard faults means you're using swap space.
Mike,
that's incorrect information, the most common cause of hard page faults
is where a process requires more memory. A hard page fault is a request
for a page of memory that is not alrea
Use Resource Monitor and look for the Memory "Hard Faults/sec".
16Gig doesn't sound like a lot of memory to me when running 8 instances of
WSJT-X and other programs.
Any hard faults means you're using swap space.Check your available swap space
too -- the old Unix rujle was swap was to be at least
Running 64bit WSJT-X Win10 Pro all updates applied.
PC i7 4790K 16 gig
Bill W2PKY
On Tue, Oct 20, 2020 at 8:11 AM Bill Somerville
wrote:
> On 20/10/2020 13:04, Bill Somerville wrote:
>
> On 12/10/2020 23:30, Bill Barrett wrote:
>
> Run 6-8 instances of WSJT-X 2.2.2 24X7.
> Have been receiving
Yes FT8;
Thanks for the reply.
Bill W2PKY
On Tue, Oct 20, 2020 at 8:09 AM Bill Somerville
wrote:
> On 12/10/2020 23:30, Bill Barrett wrote:
> > Run 6-8 instances of WSJT-X 2.2.2 24X7.
> > Have been receiving this set of codes regularly after the app runs for
> > several days sometimes as much as
Hi Michael,
WSJT-X v2.3.0 RC1 has some corrections to defects in Tx start time. Also
audio buffers sizes have been increased which may add some latency.
73
Bill
G4WJS.
On 20/10/2020 13:32, Black Michael via wsjt-devel wrote:
Side-by-side here - 2.2.2 on the left and 2.3.0rc1 on the right show
TS590S
Alan G0TLK, sent from my mobile device
On 20 October 2020 13:37:24 Bill Somerville wrote:
Hi Alan,
same question for you, what is your Rx please?
73
Bill
G4WJS.
On 20/10/2020 13:20, Alan Groups wrote:
Hi, just tested 2.3.0 RC1 for this:
Running Meinberg NTP, time.is reporting exact (+
Can you guys confirm the behavior?Looks like I can modify hamlib pretty easily
to achieve restoring the band settings from the band stack.
But what happens if you change band settings on the rig and change bands. Do
you need to put it in the band stack yourself or are the settings always
rememb
Also...this sounds a lot like either a memory leak or memory fragmentation.
That error message means the underlying allocation in the system was unable to
get a large enough memory block to satisfy WSJT-X's needs.
So either your memory usage is eating up all the memory or memory has
fragmented so
Hi Alan,
same question for you, what is your Rx please?
73
Bill
G4WJS.
On 20/10/2020 13:20, Alan Groups wrote:
Hi, just tested 2.3.0 RC1 for this:
* Running Meinberg NTP, time.is reporting exact (+/- 0.01s)
* Looking at 7MHz FT8 Rx - by eye most DT numbers seem to be in the
0.3 to 0.
Hi, just tested 2.3.0 RC1 for this:
* Running Meinberg NTP, time.is reporting exact (+/- 0.01s)
* Looking at 7MHz FT8 Rx - by eye most DT numbers seem to be in the
0.3 to 0.4 range with quite a few outliers at even greater offsets
including +1's
* On 14MHz FT4 (no FT4 signals on 7MHz!) m
On 12/10/2020 23:30, Bill Barrett wrote:
Run 6-8 instances of WSJT-X 2.2.2 24X7.
Have been receiving this set of codes regularly after the app runs for
several days sometimes as much as a week.
Subprocess Error
Subprocess failed with exit code 3
alloc.c.269: assertion failed p:
Program receive
Hi Adrian and Rasika,
this is due to a quirk of some Yaesu rigs, which I consider to be a
defect. If you change bands using the band buttons the destination band
settings for some parameters like IPO and aerial selected are recalled
from last use on that band. OTOH if the band is changed by a
On 20/10/2020 13:04, Bill Somerville wrote:
On 12/10/2020 23:30, Bill Barrett wrote:
Run 6-8 instances of WSJT-X 2.2.2 24X7.
Have been receiving this set of codes regularly after the app runs for
several days sometimes as much as a week.
Subprocess Error
Subprocess failed with exit code 3
allo
On 09/10/2020 20:51, Bobby Chandler wrote:
Has anyone noticed the DT being off by .3 to .4 on FT8 on the
2.2.0-rc1 version, even when time.is shows exact? It is OK on FT4 and
V2.2.2, always within about .1. Seems maybe a delay in the processing
that was not there in earlier versions.
Bobby/N
Ras Yes you are correct, tested here.
@ Bill, the FTDX101.. does not retain band IPO setting when band is
changed from wsjtx, tested here on rc 2.3.0.
The radio does retain these settings when band is changed at the radio.
73
Adrian Fewster
On 20/10/20 9:04 pm, Rasika Liyanage via groups
25 matches
Mail list logo
