View Single Post
Old 05-20-2020, 05:42 AM   #12
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,
Quote:
Originally Posted by JSWolf View Post
One thing I just thought of is to switch to the 6-bit Java. 32-bit Java could be running out of memory given it only has a 3GB limit. If the OS is 32-bit, it's time to update that to 64-bit as 32-bit Java is rather poor these days.
if it is the java code in the CC app that is struggling, very few mobile devices have >3Gb memory.
3GB memory should be plenty for moving a 300Mb book- all it is doing is a file copy

it may help, with screenshots of source folders , to establish at what size the app crashes. I recall moving a 100Mb sized book with an older version, of CC [ from content server ,. not cloud. i have not re-tested that with latest version ]

it may also help to test if the crash is only with cloud solution or if it is also with library on SD card or with calibre content server/wireless device connectivity options
stumped is offline   Reply With Quote