On 28/04/2021 03:21, Roger Rehr W3SZ wrote:
Hi All,
I would ordinarily not report this because I would have assumed that
it was an idiosyncratic event related to my particular setup, but the
crashes which occurred yesterday (4-26-2021) and which I describe
below happened twice simultaneously to both me and my QSO partner K1RZ
with all WSJT-X windows simply disappearing from our screens without
giving any error messages while we were testing our terrestrial path
on 10 GHz using Q65-60D. When the crashes occurred, I DID NOT need to
go into the task manager and shut down a still-running WSJT-X
instance. I was able to restart WSJT-X just by double-clicking its
icon on the desktop, as usual.
I was using Windows 10 version 20H2 and Dave was running Windows 10
version 2004 and as noted in the subject heading we were both running
WSJT-X 2.4.0-rc4.
We were both using CAT control of our rigs (my SDR was identified to
WSJT-X as a TS-2000 and Dave was CATing via DX Lab Suite Commander.
The crashes occurred simultaneously at each of our locations just
before 1539 UTC and again just before 1548 UTC, shortly after we had
both changed modes to Q65-60D with our radios tuned to 10368.200 MHz.
I had an additional identical crash at 1542 but Dave had no crash at
that time. I don't have the exact times for the crashes, but rather
just the times obtained from the WSJT-X syslog indicating when either
of us restarted the program right after the crash. At least one of
the crashes that occurred at both sites seemed to occur at the "top of
the minute" just as a new minute started. Note that there are no "Log
Finish" events preceding the "Log Start" events in the syslog excerpts
below at the times we noted the crashes, consistent with a WSJT-X
crash occurring and causing the program to exit without writing a "Log
Finish" event..
Hi Roger,
although they are not particularly helpful, some information that may
help should be recorded in the Windows Event log . The most useful
diagnostic would be the saved .WAV file that causes the crash, assuming
the decoder is the source of the crash which is likely.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
