KOReader doesn't open large, complex ebooks?
#1  SbAgOoTs 07-22-2019, 12:35 PM
Hi all,

I recently found out that KOReader (on any platform, Android app included) can't open large (i.e.: having a lot of pages) and complex (i.e.: having a lot of links, references, etc...) epubs.
As a test book anybody can access to for free I use the 2013 revision of Jehovah’s Witnesses Bible ( ): never been able to open it, KOReader stays "thinking" forever...
Any idea?
It's really a bug?


#2  NiLuJe 07-22-2019, 12:45 PM
Opening this one up with Sigil is a fun experience, too .

It feels like there's *at least* as much markup as text, so, yeaaaaaah, it could probably use a bit of simplification to make it easier to parse.

It's probably blowing all kinds of CRe limits as-is. @poire-z has a few gnarly test books for these kind of things, so he may have some more useful input here.

#3  NiLuJe 07-22-2019, 01:06 PM
Well, turns out it opens just fine over here .

It might take a good long while on slower devices, but it will open & work when it does. Subsequent openings will use the cache, and should be much faster, as long as you don't thrash the cache by requesting a formatting change that requires a re-render.

FWIW, it takes a whopping 4s and change to open on my desktop, which is far faster than @poire-z's gnarliest test books, I think ;p.

07/22/19-19:16:12 DEBUG CreDocument: loading document...
07/22/19-19:16:16 DEBUG CreDocument: loading done.
(And generates a fun 14MB cache file ).

#4  SbAgOoTs 07-22-2019, 01:18 PM
Mmmhhh, how long?
I have an Aura One (I suppose not a slow device....) and I left it working for more than 20 minutes without success...
The same on an Android device.

#5  NiLuJe 07-22-2019, 01:24 PM
I'd monitor it over shell, to see if it didn't just murder the OS or something, although that shouldn't happen either.

I seem to recall previous issues discussing this kind of things that it might take a couple minutes on an actual eInk device, but 20 seems overkill. Especially given the 4s it took on my desktop.

And, yeah, the Aura One definitely falls in the "slow" basket. A decent modern mid to high-range phone should be far faster, for instance.

#6  NiLuJe 07-22-2019, 01:31 PM
Yup, two minutes on my H2O (which should be a tiny bit slower than your One), which tracks with what I remembered .

(And it required only something shy of 200MB of RAM, so, shouldn't be a strain to the OS either).

07/22/19-19:27:28 DEBUG CreDocument: loading document...
07/22/19-19:29:34 DEBUG CreDocument: loading done.
Then a few seconds when cached:

07/22/19-19:33:23 DEBUG CreDocument: loading document...
07/22/19-19:33:28 DEBUG CreDocument: loading done.

#7  Frenzie 07-22-2019, 03:01 PM
Quote NiLuJe
A decent modern mid to high-range phone should be far faster, for instance.
It took about 42 seconds on my 2015 Zenfone 2 with a blisteringly fast Intel Atom.

It took only about 35 seconds on my 2018 Xperia XA2 with some ARM Snapdragon 630 contraption.

To get to Kobo Aura One speeds I'd have to use my low-mid-range 2011 Xperia Ray. (Unfortunately I can't because the bottom half of the touch screen suddenly stopped working.)

#8  Frenzie 07-22-2019, 03:17 PM
Fun fact: calibre took longer to open that than KOReader.

#9  Marinolino 07-22-2019, 05:11 PM
It took Koreader (v2019.05-8-g...2019-05-18) on my Kobo Aura One (software ver. 4.14.12777) less than two minutes i.e. 1 min 39 sec., and then after quickly jumping to pages 1000, 2000 and 10 000 using go-to function, as well as several random links, I've closed it, and then it took 3 seconds to open it again, after I've opened several pdf and epubs beforehand, and then after 10-15 minutes it took 4-5 seconds after I went to Nickel and back to Koreader.

I don't have a lot of books uploaded in Koreader or Nickel, about one hundred, and 5 GB of 8 GB is still available.

#10  NiLuJe 07-22-2019, 05:47 PM
@Marinolino: Many thanks for that random drive-by testing on the exact same device! .

  Next »  Last »  (1/4)
Today's Posts | Search this Thread | Login | Register