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 much it can' satisfy a big enough block. Could also mean you don't have enough swap space as swap will be used if needed. Mike W9MDB
On Tuesday, October 20, 2020, 07:09:32 AM CDT, Bill Somerville <g4...@classdesign.com> 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. _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel