I'll definitely give that a shot then.

Ah yes, that would be important to know. I've been using the GUI as I remote into my server frequently working on projects, and it's easy enough to open when it's right there. And sounds good regarding that taking a while as epub would be nice. And consistent isn't the idea I was meaning. I probably shouldn't be writing posts in bed at 1am. XD My point was I'm used to languages with aggressive garbage collection and/or I take care of it aggressively myself. Makes sense though now. I've made a point of avoiding learning java, so am fairly ignorant when it comes to things like that with it.

I might try moving ubooquity over to my linux VM for now and see if that helps things if it keeps not responding.

Ah, in my case I was talking about both your and Justin's problems and got you guys mixed up. And no, I didn't see any heap or other errors unless they would have been sent to err on a cmd window rather than the log file, which I can check if that's the case. And interesting regarding the memory issues. I'm used to programming in c/c++/python where memory usage is mostly to entirely consistent and/or predictable. And ubooquity on the server side is still responsive when this happens. I can change settings, scan for new comics, and close the program. More interestingly however, hitting the save and restart button doesn't throw any errors in the log file, and the log shows that its restarted, but its still not accessible. Only if I close the entire running instance and restart it will I get access to it again.

So I'm having a similar problem on a Windows Server 2012 machine with 64-bit java 1.8.0_71. On initial startup, ubooquity idles at 145.5MB ram usage. I currently have my scan interval set to 15 minutes as I've been updating my database frequently and have it running headless. Watching the ram usage, if I manually launch a new library scan the usage jumps and then settles higher than it was before the scan. The difference doesn't seem to have any kind of consistency to it. I saw values between 600K and 2MB. That being said, my end result is the same where the page just stops responding.

Looking at my ram usage for ubooquity the last time it stopped responding had it at 800MB used. I can understand the potential for high ram usage with Tom as he has 2TB of comics, but I only have a little less than 1GB in 112 comics right now, so I feel like that wouldn't be the issue. Also, my logs say everything is running just fine. I also have the same temp fix where if I leave a connection to ubooqity open it has no issues staying connected. But if I disconnect, one night is enough to get it to not respond again.