Yes, it appears from the back trace to be a bug in Qt's Accessibility code of some sort:
Code:
Thread 0 Crashed:: CoverWorker Dispatch queue: com.apple.main-thread
0 libobjc.A.dylib 0x191be9820 objc_msgSend + 32
1 QtGui 0x10d2729b8 QAccessibleCache::removeAccessibleElement(unsigned int) + 144
2 QtGui 0x10d6a2754 QAccessibleCache::deleteInterface(unsigned int, QObject*) + 3704
3 QtWidgets 0x104c24d70 0x104924000 + 3149168
4 QtGui 0x10d69b34c QAccessible::updateAccessibility(QAccessibleEvent* ) + 156
5 QtWidgets 0x104c2f074 QAbstractItemView::setRootIndex(QModelIndex const&) + 168
6 QtWidgets 0x104c6d9c8 QListView::setRootIndex(QModelIndex const&) + 84
7 PyQt6.QtWidgets.so 0x1054d7908 sipQListView::setRootIndex(QModelIndex const&) + 136
8 QtWidgets 0x104c2ed80 QAbstractItemView::reset() + 972
9 PyQt6.QtWidgets.so 0x1054d7870 sipQListView::reset() + 120
10 QtCore 0x101fd881c 0x101ea4000 + 1263644
11 QtCore 0x1021cb5b8 QAbstractItemModel::endResetModel() + 776
12 PyQt6.QtCore.so 0x102688be8 meth_QAbstractItemModel_endResetModel(_object*, _object*) + 104
13 Python 0x1017f9db0 cfunction_call + 96
14 Python 0x1018e27d4 _PyEval_EvalFrameDefault + 174964
But I thought all of these macOS Accessibility Issues were tracked down and fixed *before* Qt 6.8.2.
What version of Qt does this version of Calibre use?