Quote:
Originally Posted by NSILMike
It is randomly happening again, and I have figured out something that might help debug it...
Recall that sometimes I thought it took a laptop reboot to cure the issue. While that might have been true, I am not so sure now. When I can't connect, my first try was to shut down Calibre and restart that. I got curious and opened the windows task manager. I noticed that it takes the two Calibre processes (calibre.exe and calibre-parallel.exe) up to around 15 seconds to fully shut down when I have the issue. Otherwise they both shut down in maybe a second or two... If I restart Calibre before the two are fully shut down, the problem persists. If I wait, it is cured. (Thus my suspicion that the reboot was only helping by killing the two calibre processes.)
|
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:
- Are you running conversions or other jobs when you connect?
- Are you running calibre 2.27? There were a few changes in that release that improved connection reliability.