Details
-
Bug
-
Resolution: Fixed
-
P2: Important
-
None
-
6.4
-
None
-
Coin Precheck run, see URL of crash-log for details.
Description
While trying to fix QTBUG-102334 I've tripped over a crash in tst_QPointer::threadSafety().
My proposed fix for QTBUG-102334, that I was testing when this showed up, has (according to QTBUG-102334's reporter, testing my patch) some thread-safety issues, but (given how small my change is, this problem is probably pre-existing and merely brought to light by my change, and) I see no sign of QSettings (the only code changed by my proposed fix) in the tst_QPointer crash-log:
Stack: # 1: QTest::toString() - 0x00007FF99D777B40 # 2: UnhandledExceptionFilter() - 0x00007FF9BD412090 # 3: memset() - 0x00007FF9BFC0A000 # 4: _C_specific_handler() - 0x00007FF9BFBF3500 # 5: _chkstk() - 0x00007FF9BFC08140 # 6: RtlRestoreContext() - 0x00007FF9BFB95120 # 7: KiUserExceptionDispatcher() - 0x00007FF9BFC07250 # 8: QBindingStorage::reinitAfterThreadMove() - 0x00007FF984C105C0 # 9: QObjectPrivate::reinitBindingStorageAfterThreadMove() - 0x00007FF984C0C540 # 10: QThread::exec() - 0x00007FF984CA7BD0 # 11: QThread::start() - 0x00007FF984D268E0 # 12: BaseThreadInitThunk() - 0x00007FF9BEBB54D0 # 13: RtlUserThreadStart() - 0x00007FF9BFB64830
Attachments
Issue Links
- blocks
-
QTBUG-102334 QSettings / QDateTime incompatible when switching from Qt6 -> Qt5
- Closed
- duplicates
-
QTBUG-101681 tst_QPointer::threadSafety() is flaky (probably race condition)
- Closed