View Single Post
Old 05-08-2015, 12:33 PM   #18
NSILMike
Guru
NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.NSILMike turned on, tuned in, and dropped out.
 
Posts: 735
Karma: 35936
Join Date: Apr 2011
Location: Shrewsury, MA
Device: Lenovo Android Tablet
Quote:
Originally Posted by chaley View Post
Thanks for the feedback. I can see only one reason why having a worker process would block connections, and that way is supposed to be almost impossible to trigger, requiring an event that happens in a millisecond window.

Questions:
  1. Are you running conversions or other jobs when you connect?
  2. Are you running calibre 2.27? There were a few changes in that release that improved connection reliability.
I would typically be running skype, and a browser (chrome and/or Firefox depending on what I am doing at the moment for work.) Calibre could be downloading or converting to mobi, but probably not as I download many news sources at specific times, and typically sync to Calibre Companion when all are done.)
And I am always running the current version of Calibre, as I would download and install the same day it notifies me of the upgrade. So, now and since last Friday (when the updates seem to arrive) I am on 2.27
By the way, as mentioned it seemed better for a while, and has come back. Initially it was happening maybe 40-50% of the time. Now it is maybe 1 out of 4 or 5 days.

Last edited by NSILMike; 05-08-2015 at 12:35 PM.
NSILMike is offline   Reply With Quote