Crashes on macOS ARM using Sockets
-
wrote on 5 Aug 2024, 13:24 last edited by jazzco2 8 May 2024, 13:25
Hi all,
since we added the macOS ARM platform (as of April '24) we experienced several random crashes. On the other platforms Windows, Linux, and also on macOS x86 this doesn't occur. It looks like an QObject has been deleted without removing all internal references.
Latest crashes with a build on Qt 6.7.2. From the user perspective this looks all alike. You enter a special mode that opens a local socket communication to another application, it works some time and then crashes. (But as mentioned: This does NOT happen on macOS x86)
Anyone who has similar issues with Qt on macOS ARM?
Regards- This seems to notify an invalid object:
0 QtCore 0x104d7bf38 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 168 1 QtCore 0x104eda78c 0x104cf8000 + 1976204 2 CoreFoundation 0x19501d1e4 __CFSocketPerformV0 + 924 3 CoreFoundation 0x194ff1eb0 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 4 CoreFoundation 0x194ff1e44 __CFRunLoopDoSource0 + 176 5 CoreFoundation 0x194ff1c14 __CFRunLoopDoSources0 + 340 6 CoreFoundation 0x194ff07a0 __CFRunLoopRun + 828 7 CoreFoundation 0x194fefe0c CFRunLoopRunSpecific + 608 8 HIToolbox 0x19f78b000 RunCurrentEventLoopInMode + 292 9 HIToolbox 0x19f78ae3c ReceiveNextEventCommon + 648 10 HIToolbox 0x19f78ab94 _BlockUntilNextEventMatchingListInModeWithFilter + 76 11 AppKit 0x198848970 _DPSNextEvent + 660 12 AppKit 0x19903adec -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700 13 AppKit 0x19883bcb8 -[NSApplication run] + 476 14 libqcocoa.dylib 0x1038f9f40 0x1038e4000 + 89920 15 QtCore 0x104d85abc QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 540 16 QtCore 0x104d7c5b8 QCoreApplication::exec() + 112 17 studio 0x103058284 main + 328 18 dyld 0x194b8a0e0 start + 2360- This seems to delete an invalid object:
Thread 0 Crashed:: CrBrowserMain Dispatch queue: com.apple.main-thread 0 QtCore 0x104b9977c QObject::~QObject() + 68 1 QtCore 0x104bb342c QSocketNotifier::~QSocketNotifier() + 152 2 QtCore 0x104bb3634 QSocketNotifier::~QSocketNotifier() + 12 3 QtCore 0x104d2ed68 0x104ad8000 + 2452840 4 QtCore 0x104d26018 0x104ad8000 + 2416664 5 QtCore 0x104ba24c4 0x104ad8000 + 828612 6 QtCore 0x104bb385c QSocketNotifier::event(QEvent*) + 312 7 QtWidgets 0x1026d6ec8 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 272 8 QtWidgets 0x1026d7d1c QApplication::notify(QObject*, QEvent*) + 504 9 studio 0x100e6c9b8 gams::studio::Application::notify(QObject*, QEvent*) + 24 10 QtCore 0x104b58488 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 292 11 QtCore 0x104cb1c9c 0x104ad8000 + 1940636 12 CoreFoundation 0x1865b91e4 __CFSocketPerformV0 + 924 13 CoreFoundation 0x18658deb0 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 14 CoreFoundation 0x18658de44 __CFRunLoopDoSource0 + 176 15 CoreFoundation 0x18658dbb4 __CFRunLoopDoSources0 + 244 16 CoreFoundation 0x18658c7a0 __CFRunLoopRun + 828 17 CoreFoundation 0x18658be0c CFRunLoopRunSpecific + 608 18 HIToolbox 0x190d27000 RunCurrentEventLoopInMode + 292 19 HIToolbox 0x190d26e3c ReceiveNextEventCommon + 648 20 HIToolbox 0x190d26b94 _BlockUntilNextEventMatchingListInModeWithFilter + 76 21 AppKit 0x189de4970 _DPSNextEvent + 660 22 AppKit 0x18a5d6dec -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700 23 AppKit 0x189dd7cb8 -[NSApplication run] + 476 24 libqcocoa.dylib 0x101927f50 0x101914000 + 81744 25 QtCore 0x104b62174 QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 540 26 QtCore 0x104b58b14 QCoreApplication::exec() + 112 27 studio 0x10103b790 main + 328 28 dyld 0x1861260e0 start + 2360- This seems to request a property of an invalid object:
0 QtCore 0x102eebf28 QObject::property(char const*) const + 64 1 studio 0x1010cf560 gams::studio::FileMetaRepo::fileMeta(QWidget* const&) const + 68 2 studio 0x1011aaac8 gams::studio::MainWindow::pinViewTabIndex() + 60 3 studio 0x10118b0a4 gams::studio::MainWindow::updateAndSaveSettings() + 1532 4 QtCore 0x102eeb530 0x102e1c000 + 849200 5 QtCore 0x102efdf8c QTimer::timerEvent(QTimerEvent*) + 208 6 QtCore 0x102ee3978 QObject::event(QEvent*) + 88 7 QtWidgets 0x102858b54 QApplicationPrivate::notify_helper(QObject*, QEvent*) + 272 8 QtWidgets 0x1028599a8 QApplication::notify(QObject*, QEvent*) + 504 9 studio 0x100fa0a20 gams::studio::Application::notify(QObject*, QEvent*) + 24 10 QtCore 0x102e9ff64 QCoreApplication::notifyInternal2(QObject*, QEvent*) + 212 11 QtCore 0x103013344 QTimerInfoList::activateTimers() + 1096 12 libqcocoa.dylib 0x101a7d2e4 0x101a68000 + 86756 13 CoreFoundation 0x194ff1eb0 __CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION__ + 28 14 CoreFoundation 0x194ff1e44 __CFRunLoopDoSource0 + 176 15 CoreFoundation 0x194ff1bb4 __CFRunLoopDoSources0 + 244 16 CoreFoundation 0x194ff07a0 __CFRunLoopRun + 828 17 CoreFoundation 0x194fefe0c CFRunLoopRunSpecific + 608 18 HIToolbox 0x19f78b000 RunCurrentEventLoopInMode + 292 19 HIToolbox 0x19f78ae3c ReceiveNextEventCommon + 648 20 HIToolbox 0x19f78ab94 _BlockUntilNextEventMatchingListInModeWithFilter + 76 21 AppKit 0x198848970 _DPSNextEvent + 660 22 AppKit 0x19903adec -[NSApplication(NSEventRouting) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 700 23 AppKit 0x19883bcb8 -[NSApplication run] + 476 24 libqcocoa.dylib 0x101a7df40 0x101a68000 + 89920 25 QtCore 0x102ea9abc QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) + 540 26 QtCore 0x102ea05b8 QCoreApplication::exec() + 112 27 studio 0x10117c284 main + 328 28 dyld 0x194b8a0e0 start + 2360 -
wrote on 5 Aug 2024, 13:27 last edited by
I am using QSslSocket on arm macOS with no issues of this kind. Perhaps set a breakpoint and do step by step debug once user enters this mode?
-
J jazzco2 referenced this topic on 5 Aug 2024, 13:30
-
wrote 22 days ago last edited by
Did you ever find a solution? I'm having the same problem.
3/3