as said before I do NOT use news, or periodic tasks.
idle should mean idle, not growing in footprint - lets see where it's at now - ... 198mb. I've not touched calibre since posting that it was at 190mb, & remember I started with it at circa 106mb yesterday morning.
i call this a (small) memory leak!
not enough to cause me problems but sufficient to demonstate that something somewhere needs fixing. ( but could be an issue with python as implemented in windows, not with calibre per se)
actually, the reason it's not caused me problems ever is that once a week the program gets closed & updated, which sets it back to circa 100Mb. if not for that it , & with an always-on PC, it could well go on climbing until it gobbles up huge amounts of RAM.
PS calibre surely does not hold the entire library in RAM - there are folks on here with 10,000+ books allegedly - & their loading times would be extreme if 10,000 files had to be opened & read.
so the reason I'm at 195 but you are at 240 is that your program has been active for longer, not 'cos you have more books ?
Last edited by cybmole; 10-04-2011 at 02:43 PM.
|