View Single Post
Old 04-03-2025, 08:25 PM   #17
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,932
Karma: 6361444
Join Date: Nov 2009
Device: many
A quick search of the QtBug database reveals the following *potential* cause:

https://bugreports.qt.io/browse/QTBUG-134610

I do not know the calibre codebase well enough to know if multiple signals are being temporarily disconnected from an object or not. But this is one of the only still open issues associated with the QAccessibleCache in QtBugs.

There seems to be a Qt patch for Qt 6.8.4 that detects multiple signal disconnections that removes the "destroyed" signal that the QAccessibleCache code needs to stay in sync, and to warn people not to do that.

Of course, it could just be a new Qt bug as well.

Last edited by KevinH; 04-03-2025 at 09:34 PM.
KevinH is offline   Reply With Quote