Latest iOS version of CC problem HELP!

[Steve_Haley]

Originally Posted by gjohn4317

I'll also take a look at the metadata for each ebook in Calibre

Did you end up finding a book with anything unusual in the metadata, e.g. the entire contents of the book in the comments, or ones with enormous cover images?

On a similar note, how large is the entire folder containing your library? The log file was reporting that the database was about 3 gigabytes in size, and I'd like to check whether that's on the same scale as the library folder itself.

[Steve_Haley]

Originally Posted by Steve_Haley

Did you end up finding a book with anything unusual in the metadata, e.g. the entire contents of the book in the comments, or ones with enormous cover images?

On a similar note, how large is the entire folder containing your library? The log file was reporting that the database was about 3 gigabytes in size, and I'd like to check whether that's on the same scale as the library folder itself.

Never mind about these; I've managed to find two things which seem to have really helped with the memory issues in the app. Assuming nothing comes up in my final testing today, I'll be submitting a new version to Apple which should greatly improve the situation. The main fix is with reducing memory when sending books, though it should also allow for a larger library in total.

(Though I wouldn't push this too far as there's currently no way to know how close to the limit you are. It's different for every device and the info stored in the books, so I can't just provide a limit. Saying that, I found in my own testing that the database size decreased from 200mb to 40mb for 1000 books. Weirdly, you were seeing a size of around 2000mb, 10x more, for a library perhaps only 3x the size. Anyway, I'm rambling...