Quote:
Originally Posted by theducks
If it crashed (self closed  ) ) it told you where the log was.
|
It didn't 'self close', the message was that "calibre.exe has stopped working and windows is looking for a solution". After a few seconds another message of the program is unresponsive and must be closed. Then the calibre window went to the background and the foreground was the blue spinning circle (frozen program) with the "close program" button to the foreground and the "close program" button was the only option - no other buttons were accessable as the program itself went to the background and the spinning blue circle of death 'greyed' it out.
It was a frozen/not-responding problem with the 'close' button being the only one available.
I corrected the auto-add feature - I chose to auto add books and selected "My kindle content" as the folder to look in. However, when I selected "save" (or was it apply???) it reverted back to "My Kindle Content 1" which does not exist! Again I directed the auto-add feature to "my kindle content", applied it and restarted Calibre and so far it has stayed there. No idea why it was going to my kindle content 1 because there is no such folder - not even hidden
It would appear that my program was resolved by adding all the calibre executables in the install folder to the blacklist in RoboForm. Since I've done that, I haven't had another crash. I've been editing books for about an hour with no issues and prior everything I did caused the crash.
"Just because a program was there for a long time, does not prevent updates from tripping things up today. A/V updates can happen daily"
True - A/V does update daily, but that's the only thing I have set to auto update. I dont like the system resources all the various program auto updates steal so I disable them and check manually from time to time.
I dont have RoboForm set to auto-update; all updates are manual and since I like the version I have, I have not updated it in a long time. Since it was not a RoboForm update that was the issue, it would appear that a recent Calibre update (likely 3 versions ago) has some issue (or bigger issue) with RoboForm. I went from years of no issues running roboform and calibre together to not being able to use Calibre and Roboform was not updated - but Calibre was. Not saying the update was bad in any way - the updates on Calibre always make things better; however, as far as RoboForm goes - the update made them not play as well together
As long as things remain stable - the problem is fixed and was fixed by blacklisting Calibre in RoboForm. Hopefully this thread can help anyone else with a crashing issue identify a possible cause.
Thank you everyone for your help.