Thread: Debug question
View Single Post
Old 09-20-2012, 12:09 PM   #2
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 29,800
Karma: 54830978
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by robin58 View Post
After the most recent update my calibre has been crashing frequently when editing metadata of newly imported books.

I've restarted calibre multiple times in debug mode but it seems never to put anything in the log file that's created after the "started in xx seconds" line after it's crashed.

Looking through my windows (7 64bit) event logs it seems the crash always involves Qtgui4.dll but that's about all the info I can get out of that and doesn't help at all.

Would the lack of anything being in the calibre crash log tend to indicate it's a conflict somewhere with another program being at fault for causing the calibre crash? Or am I completely offbase?
That DLL is used by Calibre, but not under Calibres Logging control.
BTW That DLL cause most of my crashes, about 1 or 2 a month (XP SP3) in Calibre and Sigil.
Check your System Fonts, one might be damaged. You could also try setting a different font to be used by Calibre (for the GUI, not the book) in Preferences: Look and Feel (Main Interface)

Last edited by theducks; 09-20-2012 at 02:32 PM. Reason: typo
theducks is online now   Reply With Quote