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 <[email protected]> wrote: > 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 2,612,736 bytes and would need contiguous memory. > plan=fftwf_alloc_real(NMAX1) > > > https://answers.microsoft.com/en-us/windows/forum/windows_10-performance/windows-10-fragmentation/d7ac7646-03b1-499d-9d76-99502b74b94f > > https://www.design-reuse.com/articles/25090/dynamic-memory-allocation-fragmentation-c.html > > Mike W9MDB > > > On Tuesday, October 20, 2020, 09:52:43 AM CDT, Bill Barrett < > [email protected]> wrote: > > > 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 < > [email protected]> wrote: > > 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 2X physical memory. > I just checked mine and I've got a 5gig swap space for my 32gig > memory...but it doesn't get touched (usually). > https://ccm.net/faq/43000-adjust-default-virtual-memory-size-on-windows-10 > > > Also watch the memory to see how much free space and standby it shows over > the days of running.... > > [image: Inline image] > > Mike W9MDB > > > > > On Tuesday, October 20, 2020, 08:31:04 AM CDT, Bill Barrett < > [email protected]> wrote: > > > 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 <[email protected]> > 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 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 received signal SIGABRT > Process abort signal. > > This happens to most of the running instances. > When this happens the size of the windows gets large on my 4K monitor, > like the resolution changes. > The computer locks up. > > Any ideas? > -- Bill W2PKY > > > Hi Bill, > > is this always using the same mode? If so then which mode? > > 73 > Bill > G4WJS. > > Hi Bill, > > also are you running a 32-, or 64-bit version of WSJT-X? > > 73 > Bill > G4WJS. > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > -- > Bill Barrett > 352-437-4758 > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > _______________________________________________ > wsjt-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > > > > -- > Bill Barrett > 352-437-4758 > -- Bill Barrett 352-437-4758
_______________________________________________ wsjt-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wsjt-devel
