View Single Post
Old 03-15-2011, 08:28 AM   #8
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,732
Karma: 2197770
Join Date: Oct 2010
Location: Australia
Device: Kindle Oasis
I've been continuing to battle with this extremely intermittent issue. Every time I can replicate it a couple of times in a row I get all excited as to a possible scenario I can give you and then of course it fails to happen the next 20 times I try it.

What I have concluded is that while it does occur using some of my plugins, I can also get it to occur when not even loading my plugins (i.e. normal Calibre usage). I believe (one) of the culprits is the cover browser. Certainly with it visible I have the highest chance of repeating the issue. I am on Windows 7 64-bit, one of my plugin testers (dwanthny) is on Windows XP and we get the same QObject:killTimers message before Calibre immediately dies.

I have had this happen while sitting in the library view doing nothing and typing this post. Prior to that I managed to get it to happen while using the edit metadata dialog to "Generate default cover" for 50 books. It got about 22% of the way through according to the progress dialog and then crashed. this was after a clean start of calibre-debug -g with not starting any of my plugins

My normal view lately has been with the tag browser, cover browser and book details panel visible. But it seems to be the cover browser that most often causes this issue to show itself.

Any ideas/suggestions welcomed - particularly if chaley/Kovid et al could re-cast their eye over the threading around the cover browser and see if they can spot a possible cause.
kiwidude is offline   Reply With Quote