Locked Re: Portable calls crashing WSJT-X Version 2.5.3 #Windows10 #windows11 #decode

Rob Kivell

Ditto here. Replied to HC1MD\2 CQ call on 20m (if I remember correctly) this morning. He responded and WSJTX crashed. That was the first time the program ever just cashed. It was the last QSO I attempted for that particular session . Just thought it was one of those things. I thought I hit the wrong button but I’m not sure now . I’m using the latest 64 bit program W10 and a Dell laptop. I won’t be back on air tonight but imagine I will hit it again in the morning.


On Tuesday, December 14, 2021, 2:54 PM, Andrea Tommasi <atommasi@...> wrote:

Also i have similar behaviour trying to answer with tx2 (report) to hb0/hb9..... some days ago when wsjtx must send rr73 it crash, to run again wsjtx i need to kill jt9.exe process before.
Tryed two times with same crash.
Win10home 64 bit on xeon cpu and 6 gb ram, i have other qso with hb0/hb9... but never crash with previous release.

73 ik4idp

Il 14 dic 2021 20:48, Max NG7M <ng7m@...> ha scritto:

Jim, W7CT and I have been duplicating an issue with 2.5.3 (64-bit version if that matters) this morning, where you start to work a portable call and the UI just terminates...a WSJT process is left running, so you can't start another instance of WSJT until you find terminate the process.  We have duplicated this issue trying to work portable callsigns.  Specifically, N6QEK/KL7, HC1MD/2 (12M), AE5KO/6 (20M).  Not that the bands matter.  But these were actual callsigns that caused the crash.  And I was able to duplicate it after a restart with N6QEK/KL7, he certainly is wondering why stations just stop completing the exchange if they are running 2.5.3. :)

Anyone else noticed this with 2.5.3?

This has been duplicated with Windows 10 and Windows 11.  NG7M running Windows 11 (64 bit obviously) and W7CT running 64bit Windows 10.

Max NG7M

Join {main@WSJTX.groups.io to automatically receive all group messages.