View Single Post
Old 05-22-2020, 03:31 AM   #24
stumped
Wizard
stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.stumped ought to be getting tired of karma fortunes by now.
 
Posts: 3,305
Karma: 10259306
Join Date: May 2016
Device: kobo forma, Kobo Libra, Huawei media Tab, fire HD10, PW3 HDX8.9,
I tested with a 270Mb book and the same version of the app, on a 2Gb Ram tablet,& that worked Ok ( but not from G Drive) SO i think you need to eliminate G drive as a suspect.
I assume you have the big books in calibre library as well as in cloud - so can you connect CC to calibre content server or as a wireless drive and retest. if the error goes away but returns when you revert to G drive that will be a big clue. Maybe the API that CC uses for G drive needs attention.


as to G drive breaks calibre... " its been known for years that operating a live library in G drive will do damage, as will a live library in other cloud that is also background syncing while calibre is working. A COPY of calibre library in any cloud , for remote access when main library PC is off, shoudl be safe.
stumped is offline   Reply With Quote