|
Worker processes are used for many things in calibre, but they are always killed when quitting calibre. If that is not happening on your system there is something wrong with your system. And note that worker processes are all designed to sleep unless they are actually doing something, so they dont use any resources. For example, the calibre GUI will keep a single worker process in standby so as to to be able to add/save books fast without waiting for worker startup (which is slow in python). Similarly, the editor will keep two standby processes per instance, used for rendering the preview panel and auto-complete. Neither of these processes actually run unless there is work to be done.
In your list below, 1. look suspicious, that is a short lived worker process used to move books to the recycle bin when deleting books. If it is hanging around then it is likely that something is wrong witht he recycle bin on your system.
|