I’ve also had this happen on maybe four occasions when using FT8. RC4 on Windows10 running in Parallels on MacBook. Seems to be random. Resolved by killing the JT9 process in Task manager and restarting WSJT-X
> On Sep 19, 2022, at 9:34 AM, Bill Lederer via wsjt-devel > <wsjt-devel@lists.sourceforge.net> wrote: > > I've had three segfaults on rc4. > > One when I had just started up, another after I had been running for a little > while, and a third when I clicked the "menus" button. No other correlation > that I could find. I didn't find a "core" file. > > On Sun, Sep 18, 2022 at 10:32 PM Black Michael via wsjt-devel > <wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>> > wrote: > About how long were you running when this happened? > > I also had a segfault when WSJTX was just decoding but it was probably 20 > hours of runtime. > > Mike W9MDB > > > > > On Sunday, September 18, 2022 at 08:49:23 PM CDT, Gary McDuffie via > wsjt-devel <wsjt-devel@lists.sourceforge.net > <mailto:wsjt-devel@lists.sourceforge.net>> wrote: > > > I seldom report problems that I might have because I don’t usually have > enough notes on all the details, but this one seemed serious enough that I’ll > tell you what I know about it. Can I duplicate? Of course not, yet. I’ve > been using RC4 since it came out, so it's likely a one-off event. I’ve not > had previous problems. > > I was on 17M FT8, made a few contacts with no problem. After the last one > logged, I hit the FT4 button and jumped up the band as I frequently do when > things are busy. I worked one station on FT8 and logged it. After it > logged, the program simply closed itself - gone. > > When I tried to restart WSJT-X, it failed, giving me the following error: > Sub Process Error > Failed to close orphaned jt9 process > I am very familiar with the jt9 task error, and haven’t had one for a long > time, but I think this is the first time I’ve had the process error. WXJT-X > did not load. When I clicked on the error to close it, it was replaced by a > second one that said simply: > Fatal error > Sub-process error > Acknowledging that one closed the error message & it went away. > > Any time I tried to repeat the reloading of WSJT-X, the same errors popped > up. In order to get it back up and running, I had to reboot the system > entirely. It seems to be running smoothly since then, as it had before. I > suspect everything is fine and this was just a glitch. > > Gary - AG0N > > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > <https://lists.sourceforge.net/lists/listinfo/wsjt-devel> > > > -- > --w8lvn-- > _______________________________________________ > 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
