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

On 12/14/2021 3:48 PM, Max NG7M wrote:

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

Yes, exact same thing happened to me today.

Rick VE1GN

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.

This issue cannot be duplicated on LINUX openSUSE Leap 15.3 with a version built from the source code published at https://sourceforge.net/p/wsjt/wsjtx/ci/master/tree/.
The latest commit included is 69f9ec, Author: Joe Taylor <joe@...> Date: Tue Dec 7 10:33:39 2021 -0500

I worked MW0USK/2ZE (40m) and 2E0CVN/2ZE (30m) without any problem.

73, Walter DL8FCL

On Wed, Dec 15, 2021 at 11:24 AM, Charles Suckling wrote:

Hi Walter

I tested 2.5.3 Windows 64 bit (same commit as you) with a few simulated
messages containing reports from the compound call station (Q65) and did not
see any issues.  Wondering if the stations reporting the problem were using
the messages generated by the program in TX1-6 or were typing in responses
themselves.

73

Charlie DL3WDG

Hi Charlie,

it would be interesting to hear from the authors if this code is also the base of the of the binaries published on https://physics.princeton.edu//pulsar/K1JT/wsjtx.html.

73, Walter DL8FCL

I too am seeing this crashing when using WSJT-X V2.5.3 (Win 10, 64-bit) with certain portable calls. Using along side HRD for rig control and logging.
I can't get it to happen every time, but it's only been with /stroke calls.
Upgraded to 2.5.3 yesterday and noticed the first crash in QSO with several Japanese FT8 stations.

Each time, I'm replying to a CQ call or a blind call from another station mid-QSO. I am double clicking on the RXFrequency decode window to grab their call and auto gen messages.
Not sure if it matters, but I'm using split with the "Hold TX Freq" option to send. Also using Deep Decoding.

The process for "jt9 - WSJT-X slow mode decoder" must be manually killed to be able to re-launch WSJT-X.

Radio: Kenwood TS-2000 w/Signalink USB interface.

Win10 Event Viewer App Error record:
Faulting application name: wsjtx.exe, version: 2.5.3.0, time stamp: 0x61b0e1e7
Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0xa280d1d6
Exception code: 0xc0000374
Fault offset: 0x00000000000ff199
Faulting process id: 0x8b4
Faulting application start time: 0x01d7f1fd6c5bf4f2
Faulting application path: C:\WSJT\wsjtx\bin\wsjtx.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: c7cb1266-3a41-46df-98f1-a78927471446
Faulting package full name:
Faulting package-relative application ID:

Log Name: Application
Source: Application Error
Date: 12/15/2021 2:27:57 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: BEAST
Description:
Faulting application name: wsjtx.exe, version: 2.5.3.0, time stamp: 0x61b0e1e7
Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0xa280d1d6
Exception code: 0xc0000374
Fault offset: 0x00000000000ff199
Faulting process id: 0x8b4
Faulting application start time: 0x01d7f1fd6c5bf4f2
Faulting application path: C:\WSJT\wsjtx\bin\wsjtx.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: c7cb1266-3a41-46df-98f1-a78927471446
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" />
<EventID Qualifiers="0">1000</EventID>
<Version>0</Version>
<Level>2</Level>
<Task>100</Task>
<Opcode>0</Opcode>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2021-12-15T22:27:57.6028305Z" />
<EventRecordID>31293</EventRecordID>
<Correlation />
<Execution ProcessID="0" ThreadID="0" />
<Channel>Application</Channel>
<Computer>BEAST</Computer>
<Security />
</System>
<EventData>
<Data>wsjtx.exe</Data>
<Data>2.5.3.0</Data>
<Data>61b0e1e7</Data>
<Data>ntdll.dll</Data>
<Data>10.0.19041.1288</Data>
<Data>a280d1d6</Data>
<Data>c0000374</Data>
<Data>00000000000ff199</Data>
<Data>8b4</Data>
<Data>01d7f1fd6c5bf4f2</Data>
<Data>C:\WSJT\wsjtx\bin\wsjtx.exe</Data>
<Data>C:\WINDOWS\SYSTEM32\ntdll.dll</Data>
<Data>c7cb1266-3a41-46df-98f1-a78927471446</Data>
<Data>
</Data>
<Data>
</Data>
</EventData>
</Event>



73
Bryan Lynch
NM7C

W7CT and i were using generated responses. No responses typed in manually. Max NG7M

Win10 Event Viewer App Error record:

Faulting application name: wsjtx.exe, version: 2.5.3.0, time stamp: 0x61b0e1e7 Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0xa280d1d6 Exception code: 0xc0000374 Fault offset: 0x00000000000ff199 Faulting process id: 0x8b4 Faulting application start time: 0x01d7f1fd6c5bf4f2 Faulting application path: C:\WSJT\wsjtx\bin\wsjtx.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: c7cb1266-3a41-46df-98f1-a78927471446

Hi,

I am not a Windows expert, but just looked the date of the ntdll.dll in my Windows 10 PC and it is 13.10.2021 7:11 in one PC and 26.10.2021 14:31 in another. I have no crashes due to / in one call sign either way. Well, Windows experts could tell more about the report meaning, if that matters at all.

73, Reino OH3mA

I had it happen again just now.
I've been on FT8 all day trying to catch this happening again with more attention paid to the actual steps taken.
I had a QSO with one other "/" call today with no issue (W4ID/6) just before this attempt

(I'm NM7C)
Steps to WSJT-X Crash:

RX: AI7MH/P calling CQ
TX: (Several Attempts) AI7MH/P NM7C [report]
Change: NM7C changed split TX Freq as AI7MH/P was in active QSO (Hold Tx Freq function in WSJT-X)
TX: AI7MH/P NM7C [report]
RX: NM7C AI7MH/P [report]
CRASH and program exit.

To be clear again, the crash happened within 1-2 seconds of decoding "NM7C AI7MH/P". No buttons were pressed to make this occur.

Got the message about an orphaned JT9 process upon attempted re-launch of WSJT-X
Killed the process manually.
Launched WSJT-X again, back to normal ops.

Radio is Kenwood TS-2000
Interface is Signalink USB
WSJT-X Version: 2.5.3
Operating System: Windows 10 Pro
CAT Interface: Ham Radio Deluxe 6.7.0.391
Logging: HRD Logbook 6.7.0.391

Windows Event Viewer crash data:
Faulting application name: wsjtx.exe, version: 2.5.3.0, time stamp: 0x61b0e1e7
Faulting module name: ntdll.dll, version: 10.0.19041.1288, time stamp: 0xa280d1d6
Exception code: 0xc0000374
Fault offset: 0x00000000000ff199
Faulting process id: 0x3048
Faulting application start time: 0x01d7f2c175779c6f
Faulting application path: C:\WSJT\wsjtx\bin\wsjtx.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: 8064184e-f48e-495a-8c86-25c0d7181db5
Faulting package full name:
Faulting package-relative application ID:


I hope this helps with troubleshooting efforts.
I've never had a WSJT-X crash in years of using it until this issue.

73,
Bryan Lynch
NM7C

I posted this to the wrong thread before.

Here is a video of the app crashing with a portable call: https://youtu.be/HM9N_RLJb14

Have a good night everyone

73
Bryan Lynch
NM7C

Here's an easy way to demo the crash...

Set mode FT8
Enter DX call K0VQM/4
Generate Std Msgs
select Next 'TX 3'
enable TX
WSJT will crash on second or third transmission attempt

There may be other ways to cause the crash....

AL, K0VM

I just went back to vs 2.5.2 and everything is working and back to normal Win10, 64 bit, ICOM 7200 radio. Cheers Rob. Kk4eun Sent from AT&T Yahoo Mail for iPhone On Wednesday, December 15, 2021, 5:20 AM, Reino Talarmo wrote: #yiv0984034108 #yiv0984034108 -- _filtered {} _filtered {}#yiv0984034108 #yiv0984034108 p.yiv0984034108MsoNormal, #yiv0984034108 li.yiv0984034108MsoNormal, #yiv0984034108 div.yiv0984034108MsoNormal {margin:0cm;margin-bottom:.0001pt;font-size:12.0pt;font-family:New serif;}#yiv0984034108 a:link, #yiv0984034108 span.yiv0984034108MsoHyperlink {color:blue;text-decoration:underline;}#yiv0984034108 a:visited, #yiv0984034108 span.yiv0984034108MsoHyperlinkFollowed {color:purple;text-decoration:underline;}#yiv0984034108 p {margin-right:0cm;margin-left:0cm;font-size:12.0pt;font-family:New serif;}#yiv0984034108 p.yiv0984034108yahoo-quoted-begin, #yiv0984034108 li.yiv0984034108yahoo-quoted-begin, #yiv0984034108 div.yiv0984034108yahoo-quoted-begin {margin-right:0cm;margin-left:0cm;font-size:12.0pt;font-family:New serif;}#yiv0984034108 span.yiv0984034108EmailStyle19 {font-family:sans-serif;color:#1F497D;}#yiv0984034108 .yiv0984034108MsoChpDefault {font-size:10.0pt;} _filtered {}#yiv0984034108 div.yiv0984034108WordSection1 {}#yiv0984034108 Hi, I set up audio DX connection, whole 1 m, and got both ways:   Two Windows 10 PC’s, WSJT-X latest v2.5.3. 73, Reino OH3mA

I am having the same problem. Tried three times to complete a QSO with UT5GD/MM. Screen disappears and APP does not send last "73". Tried to restart, but get "already running" message. Have to kill "jt9 - WSJT-X slow mode decoder" task or reboot PC I can work other stations just fine.

Ken, K6UF

I was having the same problem. Didn’t want to risk missing a needed DX so I went back to 2.5.2 and all is well
Rob kk4eun 


Sent from AT&T Yahoo Mail for iPhone