MobileRead Forums - View Single Post - Soluto "thinks" Calibre crashes every time

allowingtoo · 07-09-2012, 06:30 PM

Back again. I heard back from Soluto and here's what they had to say after they had me run and send them my Windows Event Viewer Report:

"The Calibre application crash is also registered in the Event Viewer (which is a Windows service, unrelated to Soluto's crash detection), and registered there even before you installed Soluto (July 4th).

I understand this is a transparent crash, as it doesn't cause the application to stop working, and we will use this to improve our crash handler to not detect these types of crashes, but it is actually a crash, and not a compatibility issue with Soluto.

We would also like you to try out a test - disable Soluto's crash handler by right clicking Soluto's tray icon --> Advanced --> un-tick "Handle application crashes". Then go through the steps to reproduce the Calibre non-crash and let us know what happens - if you see any feedback that might be seen as a problem (like the window freezing, an error message from Windows), or if nothing out of the ordinary happens. Then go to the Event Viewer and check if it registers another application crash for Calibre.

Please keep us updated, as this scenario is very important to us, as we want to improve our detection to exclude these types of background crashes."

They then had me run another one today with the Soluto application crash feature turned off and my Windows Event Viewer is still showing that Calibre is "crashing" even though it is NOT. It's still that "silent crash"

Faulting application name: calibre.exe, version: 0.8.59.0, time stamp: 0x4ff64b39
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x43510000
Faulting process id: 0x184
Faulting application start time: 0x01cd5e1e684fae48
Faulting application path: C:\Program Files (x86)\Calibre2\calibre.exe
Faulting module path: unknown

So. Got me. Sounds like they are going to do something. I wonder what the other person's crash file looked like? Here's how they told me to do a Windows Event Viewer. It's pretty simple.

07-09-2012, 06:30 PM	#7
allowingtoo Bibliophile Posts: 159 Karma: 10 Join Date: Sep 2010 Device: Amazon	Back again. I heard back from Soluto and here's what they had to say after they had me run and send them my Windows Event Viewer Report: "The Calibre application crash is also registered in the Event Viewer (which is a Windows service, unrelated to Soluto's crash detection), and registered there even before you installed Soluto (July 4th). I understand this is a transparent crash, as it doesn't cause the application to stop working, and we will use this to improve our crash handler to not detect these types of crashes, but it is actually a crash, and not a compatibility issue with Soluto. We would also like you to try out a test - disable Soluto's crash handler by right clicking Soluto's tray icon --> Advanced --> un-tick "Handle application crashes". Then go through the steps to reproduce the Calibre non-crash and let us know what happens - if you see any feedback that might be seen as a problem (like the window freezing, an error message from Windows), or if nothing out of the ordinary happens. Then go to the Event Viewer and check if it registers another application crash for Calibre. Please keep us updated, as this scenario is very important to us, as we want to improve our detection to exclude these types of background crashes." They then had me run another one today with the Soluto application crash feature turned off and my Windows Event Viewer is still showing that Calibre is "crashing" even though it is NOT. It's still that "silent crash" Faulting application name: calibre.exe, version: 0.8.59.0, time stamp: 0x4ff64b39 Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000 Exception code: 0xc0000005 Fault offset: 0x43510000 Faulting process id: 0x184 Faulting application start time: 0x01cd5e1e684fae48 Faulting application path: C:\Program Files (x86)\Calibre2\calibre.exe Faulting module path: unknown So. Got me. Sounds like they are going to do something. I wonder what the other person's crash file looked like? Here's how they told me to do a Windows Event Viewer. It's pretty simple.