I was able to reproduce this under WinDbg and using audio loopback and my own
callsign.It happened after the transmit of <HI3T/QWRP> W9MDB R-20Which also
matches the behavior seen by Tom AA4VV Critical error detected c0000374
(6fbc.6fb8): Break instruction exception - code 80000003 (first chance)
ntdll!RtlReportCriticalFailure+0x56:
And here's the stack -- not very informative. Appears to be in the event
handler.
Gotta' love C++ name mangling.[0x0] ntdll!RtlReportCriticalFailure + 0x56
[0x1] ntdll!RtlpHeapHandleError + 0x12 [0x2] ntdll!RtlpHpHeapHandleError
+ 0x7a [0x3] ntdll!RtlpLogHeapFailure + 0x45 [0x4]
ntdll!RtlpFreeHeapInternal + 0x825 [0x5] ntdll!RtlFreeHeap + 0x51 [0x6]
msvcrt!free + 0x1c [0x7] wsjtx + 0xc04b0 [0x8] wsjtx + 0xcc5f9 [0x9]
Qt5Core!ZN9QMimeType18qt_static_metacallEP7QObjectN11QMetaObject4CallEiPPv +
0x57c75 [0xa] Qt5Core!ZN8QProcess14setEnvironmentERK11QStringList + 0x1ee
[0xb]
Qt5Core!ZN8QProcess18qt_static_metacallEP7QObjectN11QMetaObject4CallEiPPv +
0x205 [0xc]
Qt5Core!ZN9QMimeType18qt_static_metacallEP7QObjectN11QMetaObject4CallEiPPv +
0x57cab [0xd] Qt5Core!ZN18QWindowsPipeReader20emitPendingReadyReadEv + 0x32
[0xe] Qt5Core!ZN14QMetaCallEvent13placeMetaCallEP7QObject + 0x31 [0xf]
Qt5Core!ZN7QObject5eventEP6QEvent + 0x175 [0x10]
Qt5Widgets!ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent + 0x7e
[0x11] Qt5Widgets!ZN12QApplication6notifyEP7QObjectP6QEvent + 0x253 [0x12]
wsjtx + 0x218934 [0x13]
Qt5Core!ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent + 0x19a
[0x14]
Qt5Core!ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData
+ 0x175 [0x15] qwindows!qt_plugin_instance + 0x28ee [0x16]
Qt5Core!ZN21QEventDispatcherWin3213processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE
+ 0x930 [0x17] qwindows!qt_plugin_instance + 0x28d5 [0x18]
Qt5Core!ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE + 0x135 [0x19]
Qt5Core!ZN16QCoreApplication4execEv + 0x75 [0x1a] wsjtx + 0x37fcbc [0x1b]
wsjtx + 0x13c7 [0x1c] wsjtx + 0x14cb [0x1d]
KERNEL32!BaseThreadInitThunk + 0x10 [0x1e] ntdll!RtlUserThreadStart + 0x2b
On Tuesday, December 21, 2021, 02:44:35 PM CST, Tom Berry via wsjt-devel
<wsjt-devel@lists.sourceforge.net> wrote:
On 12/21/2021 3:04 PM, Joe Taylor via wsjt-devel wrote:
> Hi all,
>
> If you have seen a bug that can cause WSJT-X 2.5.3 to crash when
> callsigns like W9YOY/M or K0VQM/4 are involved, please help us to
> isolate and fix it. What we really need is a sequence of steps that
> will reliably reproduce the crash.
>
> If you have seen this bug, please let us know. If you can reproduce
> it, please send us a recipe.
>
> -- 73, Joe, K1JT
>
I have had the problem with my Apache Labs 7000 radio and HI3T/QRP.
I called him.
He answered with AA4VV <HI3T/QRP> -08
I then sent <HI3T/QRP> AA4VV R-10
Then the program exited. WSJT would not run until I rebooted the computer.
I called him again and the same think happened. (after reboot)
WSJT-X 2.5.3
Win 10
Apachie Labs 7000 Radio
FT8.
73 Tom AA4VV
_______________________________________________
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
