Thread: [Old Thread] Memory leak, Worker procees closeing
View Single Post
Old 01-06-2011, 03:48 PM   #3
theducks
Well trained by Cats
theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.theducks ought to be getting tired of karma fortunes by now.
 
theducks's Avatar
 
Posts: 31,095
Karma: 60358908
Join Date: Aug 2009
Location: The Central Coast of California
Device: Kobo Libra2,Kobo Aura2v1, K4NT(Fixed: New Bat.), Galaxy Tab A
Quote:
Originally Posted by kovidgoyal View Post
the number on the main process will not return to its original, after all you have typically added anew book to the library by a fetch news, the metadata for that book is stored in the memory.

ALso make sure you are running the latest calibre as I fixed a few mem leaks in various bits of code a few versions ago.
At 37
And I DID convert a lot
So frequent restarts (ctrl-r) are in order after a big bunch of conversions


I can deal with that.
theducks is offline   Reply With Quote