View Single Post
Old 03-07-2011, 04:05 PM   #1
kiwidude
Calibre Plugins Developer
kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.kiwidude ought to be getting tired of karma fortunes by now.
 
Posts: 4,730
Karma: 2197770
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
QObject::killTimers

Does anyone else see this message when running calibre-debug -g?

QObject::killTimers: timers cannot be stopped from another thread
QObject::killTimers: timers cannot be stopped from another thread
QObject::killTimers: timers cannot be stopped from another thread
QObject::killTimers: timers cannot be stopped from another thread

I've been seeing this sporadically for a few weeks now. It occurs when I have a dialog window (from my plugin) open in Calibre, and I just leave it open without performing any activity for a minute or two.

I didn't mind so much when it was just messages, but today it is causing the calibre process to crash and close.

My dialog is just a normal modal one inheriting from QDialog no different to my other plugins, being displayed using d.exec_(), nothing special about the controls etc.

Any ideas what may be happening? Is Calibre running some sort of operation in the background after a period of inactivity or something?
kiwidude is offline   Reply With Quote