Crash on startup

[Sneddles]

I'm consistently getting a crash in Calibre on startup on Windows XP.

It happens with both 0.8.40 and 0.8.41 and seems to be related to removing books from the library. The crash only happens after I remove one or more books from the library.

The crash is in QTWEBKIT4.DLL (4.7.3.0) at offset 0x0046B314.

If I run "calibre-debug -g" it sometimes starts and sometimes crashes with just the "Starting up" message being printed.

The crash doesn't seem to happen if I:
1. remove the book(s)
2. shutdown Calibre
3. use SQLite Administrator to cleanup the metadata.db database
4. start Calibre (using calibre.exe).

Namaste, Sneddles

[theducks]

Originally Posted by Sneddles

I'm consistently getting a crash in Calibre on startup on Windows XP.

It happens with both 0.8.40 and 0.8.41 and seems to be related to removing books from the library. The crash only happens after I remove one or more books from the library.

The crash is in QTWEBKIT4.DLL (4.7.3.0) at offset 0x0046B314.

If I run "calibre-debug -g" it sometimes starts and sometimes crashes with just the "Starting up" message being printed.

The crash doesn't seem to happen if I:
1. remove the book(s)
2. shutdown Calibre
3. use SQLite Administrator to cleanup the metadata.db database
4. start Calibre (using calibre.exe).

Namaste, Sneddles

I have had about 3 Qt crashes in the last week in Calibre (and about 5 in Sigil 5.1).
They are not all the same module crashing (the event viewer log shows what QT module).

I don't ever remember a Startup Crash, Almost always happens when updating existing metadata.

Uou may have a bad font:
Try changing the font in Preferences: Look and feel:Interface font.

[Sneddles]

Originally Posted by theducks

I have had about 3 Qt crashes in the last week in Calibre (and about 5 in Sigil 5.1).
They are not all the same module crashing (the event viewer log shows what QT module).

I don't ever remember a Startup Crash, Almost always happens when updating existing metadata.

Uou may have a bad font:
Try changing the font in Preferences: Look and feel:Interface font.

I started calibre and changed the font to Courier New and restarted.
It crashed on restart.

Looking at the event viewer, all crashes are the same module and offset.

I'm beginning to suspect a threading issue as nothing is working reliably. Calibre will crash with no changes being made to the library: just start, stop and restart.

When the dialog pops up with the crash details, the GUI has been partially drawn but it disappears before dismissing the dialog.

I usually run calibre full screen, so I changed to not use full screen and I have managed to restart it twice. I have 2 screens of different sizes, with one above the other, and the desktop extending through the top. When I started in calibre in debug mode to remove the full screen setting, there was a 2nd startup message created when I removed the full screen mode.

Namaste, Sneddles

[theducks]

I run 3 screens, of different sizes (and 1 of those in Portrait).
That does not cause problems by itself (other than losing a Windows location, now and then )

I don't use Fullscreen.

IIRC Calibre scans your Systems fonts for availability upon startup.

You may have junk in that folder that does not belong or a corrupt font. .fon and .ttf are all that belong there

[Sneddles]

Originally Posted by theducks

I run 3 screens, of different sizes (and 1 of those in Portrait).
That does not cause problems by itself (other than losing a Windows location, now and then )

I don't use Fullscreen.

IIRC Calibre scans your Systems fonts for availability upon startup.

You may have junk in that folder that does not belong or a corrupt font. .fon and .ttf are all that belong there

All files are either .fon or .ttf, but I'm not sure how to tell if one is corrupt.

I would not expect a corrupt font to affect any program unless it tried to use it, and there isn't any problem once calibre is running.

There were occasions when calibre would start without any problems, and I really don't see how a problem with a font could cause an intermittent problem.

I haven't had a crash since I took it out of full screen mode.

Namaste, Sneddles