calibre-parallel.exe process not terminating

[ShellShock]

When I start Calibre I get a calibre.exe process and a calibre-parallel.exe process. Often when I close Calibre using the UI, the calibre.exe process terminates but calibre-parallel.exe does not. This means if I try to start Calibre again it does not run - I have to kill the calibre-parallel.exe process from the previous session first to get Calibre to run. This problem seems to be more likely to occur if I start Calibre and then close it straight-away - within a minute or so.

Using Calibre 2.68, Windows 10 64 bit.

PS: I really like the new icons and splash screen - very nice.

[theducks]

Originally Posted by ShellShock

When I start Calibre I get a calibre.exe process and a calibre-parallel.exe process. Often when I close Calibre using the UI, the calibre.exe process terminates but calibre-parallel.exe does not. This means if I try to start Calibre again it does not run - I have to kill the calibre-parallel.exe process from the previous session first to get Calibre to run. This problem seems to be more likely to occur if I start Calibre and then close it straight-away - within a minute or so.

Using Calibre 2.68, Windows 10 64 bit.

PS: I really like the new icons and splash screen - very nice.

Behaves normally here (same config), worker ends shortly after closing

I test exited using both ctrl-q and the red X
I did not that the sort name (task manager) changed to The main calibre program

[kovidgoyal]

Run calibre in debug mode and post the log, the only way I know of for worker processes to hang around is if the main process crashes/does not shutdown cleanly.

[ShellShock]

I ran calibre-debug -g, and on closing Calibre got this in the log:

Started up in 2.17 seconds with 481 books
C:\Program Files\Calibre\pylib.zip\cherrypy\process\wspbus.py:225: RuntimeWarning: The main thread is exiting, but the Bus is in the states.STARTED state; shutting it down automatically now. You must either call bus.block() after start(), or call bus.exit() before the main thread exits.

I then uninstalled the iOSReaderApp and Marvin XD plugins, which I don't use anymore. That fixed the original problem but now I had a different problem - when I ran Calibre I got this:

calibre-debug -g
calibre 2.68 [64bit]  embedded-python: True is64bit: True
Windows-8-6.2.9200 Windows ('64bit', 'WindowsPE')
('Windows', '8', '6.2.9200')
Python 2.7.9
Windows: ('8', '6.2.9200', '', 'Multiprocessor Free')
Qt: Untested Windows version 10.0 detected!
Successfully initialized third party plugins: DeDRM (6, 5, 1) && Open With (1, 5, 9) && Modify ePub (1, 3, 13)
devicePixelRatio: 1.0
logicalDpi: 96.0 x 96.0
physicalDpi: 95.8113948919 x 95.9160839161
Starting up...
Started up in 2.01 seconds with 481 books

And when I closed Calibre, I saw the modal message:

Shutting down
Shutting down the content server. This could take a while...

Calibre then froze for about 110 seconds before terminating. All calibre processes were terminated at this point.

Then I remembered that last year I had enabled the content server, but I never really used it. So I went into preferences and turned off starting the content server automatically. Now Calibre closes normally - problem solved. I am not sure if the content server is meant to take that long to shut down though (if you want to use it, which I don't).

[kovidgoyal]

The content server does indeed take a while, in order to gracefully close open connections. However, that behavior will become muych more predictable with calibre 3.0 which has a re-written server that does not use CherryPy as its server engine.

[lolw]

calibre-parallel.exe process not terminating.
I am having the same kind of issue as ShellShock Wizard
I ran calibre-debug -g, and on closing Calibre got this in the log:
calibre Debug log
calibre 2.66 [64bit] embedded-python: True is64bit: True
Windows-8-6.2.9200 Windows ('64bit', 'WindowsPE')
('Windows', '8', '6.2.9200')
Python 2.7.9
Windows: ('8', '6.2.9200', '', 'Multiprocessor Free')
devicePixelRatio: 1.0
logicalDpi: 96.0 x 96.0
physicalDpi: 92.5388994307 x 92.6756756757
Starting up...
Started up in 31.16 seconds with 2 books
Worker Launch took: 0.15299987793
For some reason my Calibre library was lost from the main program, although I still have the library in my documents folder.
The error message prevents the reader from being used after importing books from my documents folders, which appear to have normal file properties when checked, and cannot be cancelled or exited in normal fashion, the only way being to restart windows 10 64bit and exit the error message box from the shutting down screen. I have used Calibre from early times, latterly using 64bit on my laptop and also my Dell desktop , both i7 processors with plenty of RAM, and never experienced this kind of problem before. I note that the debug log refers to Windows 8 but my Dell Desktop came with full Windows 10 64bit systems installed rather than upgrades from Windows 8. This probably refers to the 2.66 calibre which I installed today, after having had the same problems with 2.71 and several versions previous to 2.71.