View Single Post
Old 05-13-2017, 08:37 PM   #1
DMcCunney
New York Editor
DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.
 
DMcCunney's Avatar
 
Posts: 6,384
Karma: 16540415
Join Date: Aug 2007
Device: PalmTX, Pocket eDGe, Alcatel Fierce 4, RCA Viking Pro 10, Nexus 7
Best way to debug Calibre crash?

I just encountered a problem I have not seen before.

I have a current version of 64 bit Calibre, installed under Windows 10 Pro. I have an HP 7 Plus Android tablet running Android 4.4. My eBook library on tablet is on an external 32GB microSD card, and I use FBReader fo Android to view books on the tablet.

I connect to the tablet using a USB cable, and the tablet connects via MTP. When I plug in the tablet, Calibre sees a device is connected, and begins the process of looking for eBooks. That takes a fair bit of time, since there are thousands of volumes on device, so I do other things while I wait for it to finish. Once it's done I see Calibre's book list with checks beside volumes on device, and I can transfer new books and perhaps remove books currently on device.

Today, Calibre crashed and burned when the device was plugged in and it was searching for volumes. I got a Windows dialog box stating Calibre.exe had stopped working. In Windows Event Viewer, I saw

Code:
Faulting application name: calibre.exe, version: 2.85.0.0, time stamp: 0x591532f6
Faulting module name: wpd.pyd, version: 0.0.0.0, time stamp: 0x591532e8
Exception code: 0xc0000005
Fault offset: 0x000000000000174d
Faulting process id: 0x1994
Faulting application start time: 0x01d2cc43bb3fee13
Faulting application path: C:\Program Files\Calibre2\calibre.exe
Faulting module path: C:\Program Files\Calibre2\plugins2\wpd.pyd
Report Id: b830ef6f-f929-4aab-8e15-36580d1f56bb
Faulting package full name: 
Faulting package-relative application ID:
in the application log.

I restarted Windows and the tablet. I ran a file systems check on the volume where the Calibre library lives on Windows and it came up clean.

I shut down the tablet and ejected the 32GB microSD card, plugged it into an adapter, and ran a file systems check on it from the desktop. (The card is formatted FAT32.) That came up clean.

I restarted everything and tried again, and Calibre once again crashed communicating with the device.

What's the best way to debug this? Is there a good way to determine why the crash is occurring?

Looking at other threads here, I see that removing the Calibre metadata file on device and rebuilding might be a fix. I can do that if required - it wouldn't be the first time.

Suggestions? Comments? (NB: "Use wireless to connect to the tablet instead of a USB cable" is a very last resort matter. This has been working fine till now, and I'm averse to redoing my setup unless nothing else will work.)

Thanks in advance.
______
Dennis
DMcCunney is offline   Reply With Quote