Still planned, still high on the todo list.

But there are a lot of things I want to include in the next version, so I still probably have a few months of work before I release anything.

Thanks for the feedback !

I'm a bit late answering messages these days, but I would have suggested to update your Java version as well (although the 8u90 is already a pretty recent one).

Yes !

I have already implemented the search functionality described in the official OPDS spec:

http://opds-spec.org/specs/opds-catalog-1-1-20110627/#Search

Ok, that's not good.

The next version (no ETA) will contains big changes and some fixes related to memory consumption.

I can't promise it will fix your problem but that's the best I can offer for now.

To be honest I have no idea how Ubooquity performs with hundreds of thousands of files (apparently not that well), you're in uncharted territories.

7GB is an insane amount for something as small as Ubooquity.

But I still don't know if there is a memory leak or if the problem is limited to PDF handling.

Do you have PDF files ?

The script mentioned in the FAQ is for Linux, so it won't help you.

To set the quantity of memory Java can use, you have to launch Ubooquity using the command line.

Open a DOS shell and go in the directory which contains your Ubooquity.jar file.

Then type something like that:

"C:\Program Files\Java\jdk1.8.0_92\bin\javaw.exe" -Xmx1500m -jar Ubooquity.jar

To choose the memory amount, replace 1500m with the value you want (1500m means 1500 megabytes).

To easily reuse the command line, you can paste it in a text file and rename the text file to something.bat

Thanks for the sample file, I'll download it when I get home.

As for the solution, I am entirely dependent on the PDFBox library (used to extract PDF covers and pages).

So apart from updating Ubooquity with the latest PDFBox version each time I realease a new version, there's not much I can do.

As far as I know, Ubooquity has no timeout when it tries to access a file.

Either it fails right away, or it waits for the file to be available. On my own setup the disk takes sometimes 5 to 10 seconds to wake up and the browser just waits until the page is displayed.