Cannot open FT4 2.1.0-rc5 on Mac
Hi Again,
By the way,
I have been trying to open a newly downloaded Wsjtx FT4 2.1.0-rc5 app on a
MacBook Pro running 10.4.4 It crashes every time and I cannot open it. I use
the FT8 version all the time without problem. I have taken care of all the
memory issues, for the standard version. Am I missing something? The
beginning of the crash report is below.
Thanks
Lorin
WA1PGB/6
Process: wsjtx [1112]
Path: /Applications/WSJTX - FT4/wsjtx
2.app/Contents/MacOS/wsjtx
Identifier: org.k1jt.wsjtx
Version: v2.1.0-rc5 (2.1.0-rc5)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: wsjtx [1112]
User ID: 501
Date/Time: 2019-04-30 17:03:15.958 -0700
OS Version: Mac OS X 10.14.4 (18E227)
Report Version: 12
Anonymous UUID: EB2CC34D-9192-6924-D0D8-049FEBF57DC7
Time Awake Since Boot: 2400 seconds
System Integrity Protection: enabled
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Termination Signal: Segmentation fault: 11
Termination Reason: Namespace SIGNAL, Code 0xb
Terminating Process: exc handler [1112]
VM Regions Near 0:
-->
__TEXT 0000000108bae000-0000000109076000 [ 4896K] r-x/rwx
SM=COW /Applications/WSJTX - FT4/wsjtx 2.app/Contents/MacOS/wsjtx
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libgfortran.5.dylib 0x000000010e36e2da
_gfortran_concat_string + 23
1 org.k1jt.wsjtx 0x0000000108cf0c3d azdist_ + 93
2 org.k1jt.wsjtx 0x0000000108c15cd5
MainWindow::on_dxGridEntry_textChanged(QString const&) + 389
3 org.k1jt.wsjtx 0x0000000108c25a72
MainWindow::qt_metacall(QMetaObject::Call, int, void**) + 82
4 org.qt-project.QtCore 0x000000010de83bfd
QMetaObject::activate(QObject*, int, int, void**) + 1773
5 org.qt-project.QtWidgets 0x000000010d07d684 0x10cf29000 + 1394308
6 org.qt-project.QtCore 0x000000010de8414c
QMetaObject::activate(QObject*, int, int, void**) + 3132
7 org.qt-project.QtWidgets 0x000000010d07f186
QWidgetLineControl::finishChange(int, bool, bool) + 614
8 org.qt-project.QtWidgets 0x000000010d08031a
QWidgetLineControl::internalSetText(QString const&, int, bool) + 570
9 org.qt-project.QtWidgets 0x000000010d077cef 0x10cf29000 + 1371375
10 org.k1jt.wsjtx 0x0000000108c416cc
MainWindow::readSettings() + 1436
11 org.k1jt.wsjtx 0x0000000108c2d76d
MainWindow::MainWindow(QDir const&, bool, MultiSettings*, QSharedMemory*,
unsigned int, QSplashScreen*, QWidget*) + 31901
12 org.k1jt.wsjtx 0x0000000108cbbe35 main + 6613
13 libdyld.dylib 0x00007fff7a1753d5 start + 1
TOTAL, minus reserved VM space 834.5M 744
> On Apr 30, 2019, at 4:57 PM, Lorin Hollander <lorin.hollan...@gmail.com>
> wrote:
>
> I have experienced this countless times using FT8. In my case it raised
> complex questions about display algorithms in Windows 10. The closest
> explanations addressing these issues were given to me by Mike
> .mdblac...@yahoo.com <mailto:mdblac...@yahoo.com> Below is a copy of my
> email referencing this information to another user of this list.
>
> I would like to know what really is going on.
>
> All the best
>
> Lorin WA1PGB/6
>
> From email thread " [wsjt-devel] Feature Request” April 1 2019 ( I don’t
> think it was date related - At least I hope not)
>
> …. I believe Mike is correct in suspecting an audio dropout. He helped me
> understand the complex power-use issues in Windows 10 (made even more
> complicated when running Parallels on a Mac).. instead of using the Halt
> button (which I never tried} I have to leave the WSJT FT8 program by
> switching to Safari or email or something else for a minute or two and then
> return to find my FT8 window covered in red with incoming received calls from
> the exotic DX stations I had called for hours that seemed to never reply for
> those hours on end.
>
> While I don’t know exactly what’s happening, I had spent months with only a
> rare return call and then in frustration started to do something else to then
> return to see the fruits of the program’s labors.
>
> Fascinating question about whether the laptop display screen on the Macbook
> Pro effects the power usage of wsjtx FT8 enough to prevent or distort
> reception and/or decoding.
>
> Would love to know more from anyone about what might be going on,
>
>
>> On Apr 30, 2019, at 4:36 PM, rjai...@gmail.com <mailto:rjai...@gmail.com>
>> wrote:
>>
>> I also experience same.
>>
>> Ria
>> N2RJ
>>
>> On Tue, 30 Apr 2019 at 19:33, John T Haworth <jthawo...@charter.net
>> <mailto:jthawo...@charter.net>> wrote:
>>>
>>> Hello,
>>>
>>> I have had a large number of failed QSO’s. The station responds with Tx2
>>> within a couple of calls, but then it appears they are not decoding my Tx3
>>> response and eventually abandon the QSO. The stations are normally very
>>> strong and give an equally strong report.
>>>
>>> What could be some areas to investigate?
>>>
>>> Configuration:
>>>
>>> -Ubuntu 18.04 LTS
>>> -Elecraft K3 with USB/Sound Card upgrade
>>>
>>> Thanks and 73 John NU8M_______________________________________________
>>> wsjt-devel mailing list
>>> wsjt-devel@lists.sourceforge.net <mailto:wsjt-devel@lists.sourceforge.net>
>>> https://lists.sourceforge.net/lists/listinfo/wsjt-devel
>>
>>
>>
>> --
>> Ria Jairam, N2RJ
>> Director, Hudson Division
>> ARRL - The national association for Amateur Radio™
>> +1.973.594.6275
>> https://hudson.arrl.org <https://hudson.arrl.org/>
>> n...@arrl.org
>>
>>
>> _______________________________________________
>> 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
