Date
1 - 11 of 11
Locked v2.5.3 X64 crashes working FS/KC9FFV #stopped_working
|
Graham Alston
There is a serious bug that causes a complete crash, leaving the JT9 process orphaned, when working this callsign. The owner of this callsign has received many emails alerting him to this.
Either reboot or kill the orphaned process before re-starting. I've had other random crashes also. 73 Graham VK3GA |
|
|
|
Hello
I have been having the same issue here. I had to go into task manager and kill the process. The call sign that you gave was not the cause here. I have noticed it happening with JTAlert on. Something I really did not want to add to WSJT-x to fix the Worked stations and LoTW coloring which has not worked for me. after the new update. I turned it off and so far no crashes. This has been happening on and off all day and I just realized it may have been the JTAlert. News at 11..... 73's Gary, N2BRG |
|
|
|
HamApps Support (VK3AMA) <vk3ama.ham.apps@...>
On 25/12/2021 12:27 pm, N2BRG wrote:
I have been having the same issue here. I had to go into task manager and kill the process. The call sign that you gave was not the cause here. I have noticed it happening with JTAlert on. Something I really did not want to add to WSJT-x to fix the Worked stations and LoTW coloring which has not worked for me. after the new update. I turned it off and so far no crashes. This has been happening on and off all day and I just realized it may have been the JTAlert. News at 11.....wsjtx 2.5.3 randomly crashing on slashed callsigns is a know defect. It has nothing to do with JTAlert. de Laurie VK3AMA |
|
|
|
Mike Black
Try this version please...we believe it has been fixed now.
toggle quoted message
Show quoted text
https://www.dropbox.com/s/79rlhfyccoojpf3/wsjtx-2.5.3-win64_test7.exe?dl=0 Mike W9MDB On Friday, December 24, 2021, 07:27:20 PM CST, N2BRG <n2brg@...> wrote:
Hello I have been having the same issue here. I had to go into task manager and kill the process. The call sign that you gave was not the cause here. I have noticed it happening with JTAlert on. Something I really did not want to add to WSJT-x to fix the Worked stations and LoTW coloring which has not worked for me. after the new update. I turned it off and so far no crashes. This has been happening on and off all day and I just realized it may have been the JTAlert. News at 11..... 73's Gary, N2BRG |
|
|
|
I went for weeks without a crash. Maybe I just haven't had slashed callsigns at that time.
I'll keep a watch out for the slashers... Sadly it quits right during a call sequence or right at the pop-up for saving the contact to the log. Real bad timing. I'll check the link out, thanks. 73's Gary, N2BRG |
|
|
|
Thank you for posting the fix..I had the same problem. W2/JR1AQN crashed the program when it went to log the QSO. I had to restart the computer to start the program again. No problems running the new version today.
|
|
|
|
Thank you for posting this...mine crashed at the moment it tried to log W2/JR1AQN and required a restart of the computer to restart the application. I ran the new version all afternoon with no issues.
|
|
|
|
John Petrocelli
Hello,
toggle quoted message
Show quoted text
I saw today a similar issue with a callsign in the format "xxxxx/9" today. I saw a post here in the last couple of days about crashing with "slashed callsigns". Rather that having to restart, I have found that going to TaskManager and ending the "jt9.exe" process enabled a successful restart of WSJT-X. Just adding my 2 cents for what it is worth. I do hope this issue gets fixed in the next release of WSJT-X. Best Holidays to All !!! John R. Petrocelli - WA2HIP ¶¶¶¶¶¶¶¶¶¶ Primary Home Page: http://wa2hip.com On 2021-12-25 22:59, conradtrautmann via groups.io wrote:
Thank you for posting this...mine crashed at the moment it tried to log W2/JR1AQN and required a restart of the computer to restart the application. I ran the new version all afternoon with no issues. --
This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus |
|
|
|
Mike Black
It has been fixed for the next release.
toggle quoted message
Show quoted text
Mike W9MDB On Saturday, December 25, 2021, 08:10:54 PM CST, John Petrocelli via groups.io <jrpetro@...> wrote:
Hello, I saw today a similar issue with a callsign in the format "xxxxx/9" today. I saw a post here in the last couple of days about crashing with "slashed callsigns". Rather that having to restart, I have found that going to TaskManager and ending the "jt9.exe" process enabled a successful restart of WSJT-X. Just adding my 2 cents for what it is worth. I do hope this issue gets fixed in the next release of WSJT-X. Best Holidays to All !!! John R. Petrocelli - WA2HIP ¶¶¶¶¶¶¶¶¶¶ Primary Home Page: http://wa2hip.com On 2021-12-25 22:59, conradtrautmann via groups.io wrote: Thank you for posting this...mine crashed at the moment it tried to log W2/JR1AQN and required a restart of the computer to restart the application. I ran the new version all afternoon with no issues. -- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus |
|
|
|
John Petrocelli
Thanks Mike for the status update !!!
toggle quoted message
Show quoted text
John R. Petrocelli - WA2HIP ¶¶¶¶¶¶¶¶¶¶ Primary Home Page: http://wa2hip.com On 2021-12-26 04:17, Michael Black via groups.io wrote:
It has been fixed for the next release. --
This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus |
|
|
|
Sorry to report... I'm running version 2.5.3 69f9ec and just now I had HR5/F2JD crash the app as it went to log the QSO again.
|
|
|