So just to confirm whether or not there is a memory leak possibility, I ran operations as normal for the past few days without closing it. Here are the results:
https://imgur.com/a/wODanQn
So you can see that the used memory has almost doubled with my normal activity. Also, just to clarify, I am probably running the server in a less than ideal fashion (from the GUI, not as a dedicated process).
If it is valuable, whenever I start the calibre process one of the things I do after mounting the ramdisk is piping the output of calibre-debug to a log, which I've uploaded to pastebin for this latest session:
https://pastebin.com/3SkKPC1U
I haven't tried this without the server running yet.... essentially because my main influx of ebooks into calibre comes from entries into the server. My workflow looks like this:
1. Flexget finds a book through an RSS feed, and does a calibre-db search to see if the title or isbn exists yet.
2. Flexget passes the info onto a separate program which grabs the book and adds it via calibre-db to my "eBooks_Staging" library
3. I use the GUI to download/confirm metadata, and then copy it into the "eBooks" library with all of my other books with verified metadata
One thing I've been thinking of is running the calibre-server as its own process, and then connecting to it from the gui instead of this lazy way I'm doing now. Hope all of this helps!
Details for BetterRed: I would say the initial slowdown is apparent when browsing the grid, and just trying to interact with the buttons. I don't think it can be nailed down to a specific function, all interactions are generally slowed.