View Single Post
Old 05-27-2024, 02:26 PM   #10
pazos
cosiņeiro
pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.pazos ought to be getting tired of karma fortunes by now.
 
Posts: 1,406
Karma: 2451781
Join Date: Apr 2014
Device: BQ Cervantes 4
Quote:
Originally Posted by mathil View Post
This has been happening to me with my Kobo Libra 2. My database is, admittedly, quite large (390mb after compression with the KoboUtilities plugin, almost 4000 books on the device). I've been checking github, specifically the latest related bug report here, and am I right in understanding that this issue cannot be solved?
Everything can be solved

No idea what's your issue. Follow the bug report template and attach logs (here or in github).

Most likely your calibre json file size is above 30MB and the program switches to a utterly broken mode where it tries to parse json manually, instead of using a proper parser.

That's because the "proper parser" - rapidjson- with its current lua bindings doesn't provide a way to build the result in steps. It tries to build everything in memory until the result is ready.

So the hardcap of 30MiB is there to prevent users with <512MiB or even with +512MiB and high memory pressure to get an out of memory error.

The proper solution is to implement a parser to use for big files, but in the mean time tweaking the hardcap https://github.com/koreader/koreader...ent-1101370638 will work up to the size of your available ram.
pazos is offline   Reply With Quote