KOReader doesn't open large, complex ebooks?

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 (https://download-a.akamaihd.net/file.../7d/nwt_E.epub ): never been able to open it, KOReader stays "thinking" forever...
Any idea?
It's really a bug?

Bye

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.

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.

Code:

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

).

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.

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.

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).

Code:

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:

Code:

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

Frenzie · 07-22-2019, 03:01 PM

Quote:

Originally Posted by 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.)

Frenzie · 07-22-2019, 03:17 PM

Fun fact: calibre took longer to open that than KOReader.

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.

NiLuJe · 07-22-2019, 05:47 PM

@Marinolino: Many thanks for that random drive-by testing on the exact same device!

.

SbAgOoTs · 07-22-2019, 05:49 PM

Very interesting.
On both my devices (the Aura One and a Samsung Galaxy J4+) after 3 hours I'm still waiting to open it...
The only difference being that I'm actually trying to open the Italian version of this book: maybe it has some problems (other ebook readers open it anyway), tomorrow I will try the English version too.

SbAgOoTs · 07-23-2019, 03:09 AM

Hi guys,

as expected: wrong test book...
I confirm I can quickly open the English version I linked above as well, but I can't open (with KOReader only, other ebook readers/apps give no problems...) the Italian one: https://download-a.akamaihd.net/file.../f3/nwt_I.epub.
Any idea?

Bye

Frenzie · 07-23-2019, 05:32 AM

It worked and I think it didn't take more about 200-300 MB of RAM, so in theory it should probably succeed on a device. However, it did take an absolute eternity on my desktop.

Code:

07/23/19-11:01:22 DEBUG CreDocument: set view dimen {
    ["h"] = 1872,
    ["w"] = 1404
}
07/23/19-11:01:22 DEBUG CreDocument: set status line property 1
07/23/19-11:01:22 DEBUG made tweak css:
[END]
07/23/19-11:01:22 DEBUG CreDocument: set style sheet: ./data/epub.css and appended content (0 bytes)
07/23/19-11:01:22 DEBUG CreDocument: set embedded style sheet 1
07/23/19-11:01:22 DEBUG CreDocument: set block rendering flags 0x7fffffff
07/23/19-11:01:22 DEBUG CreDocument: set render dpi 96
07/23/19-11:01:22 DEBUG CreDocument: set page margins 22 32 22 65
07/23/19-11:01:22 DEBUG CreDocument: set floating punctuation 0
07/23/19-11:01:22 DEBUG CreDocument: set txt preformatted 1
07/23/19-11:01:22 DEBUG CreDocument: set smooth scaling false
07/23/19-11:01:22 DEBUG CreDocument: set nightmode images true
07/23/19-11:01:22 DEBUG CreDocument: set font face Noto Serif
07/23/19-11:01:22 DEBUG CreDocument: set header font Noto Sans
07/23/19-11:01:22 DEBUG CreDocument: set font size 47
07/23/19-11:01:22 DEBUG CreDocument: toggle font bolder 0
07/23/19-11:01:22 DEBUG CreDocument: set font hinting mode 2
07/23/19-11:01:22 DEBUG CreDocument: set font kerning mode 1
07/23/19-11:01:22 DEBUG CreDocument: set space condensing 75
07/23/19-11:01:22 DEBUG CreDocument: set interline space 100
07/23/19-11:01:22 DEBUG CreDocument: set gamma index 15
07/23/19-11:01:22 DEBUG Hyphenation: no algo set
07/23/19-11:01:22 DEBUG CreDocument: set hyphenation left hyphen min 2
07/23/19-11:01:22 DEBUG CreDocument: set hyphenation right hyphen min 2
07/23/19-11:01:22 DEBUG CreDocument: set hyphenation trust soft hyphens 0
07/23/19-11:01:22 DEBUG Hyphenation: keeping current crengine algo: English_US.pattern
07/23/19-11:01:22 DEBUG CreDocument: requesting DOM version: 20180528
07/23/19-11:01:22 DEBUG CreDocument: set visible page count 1
07/23/19-11:01:22 DEBUG CreDocument: loading document...
07/23/19-11:08:33 DEBUG CreDocument: loading done.
07/23/19-11:08:33 DEBUG Hyphenation: updating for doc language it : English_US.pattern => Italian.pattern
07/23/19-11:08:33 DEBUG CreDocument: set hyphenation dictionary Italian.pattern
07/23/19-11:08:33 DEBUG CreDocument: set hyphenation left hyphen min 2
07/23/19-11:08:33 DEBUG CreDocument: set hyphenation right hyphen min 2
07/23/19-11:08:33 DEBUG CreDocument: set hyphenation trust soft hyphens 0
07/23/19-11:08:33 DEBUG CreDocument: rendering document...
CRE: document loaded, but styles re-init needed (possible epub with embedded fonts)
07/23/19-11:16:19 DEBUG CreDocument: rendering done.

A peculiar difference, because once opened it looks about the same at a glance. calibre concurs by opening it in some 8-10 seconds much like the other one.

NiLuJe · 07-23-2019, 11:06 AM

Yup, same here...

Code:

07/23/19-16:55:25 DEBUG CreDocument: loading document...
07/23/19-17:00:04 DEBUG CreDocument: loading done.
07/23/19-17:00:04 DEBUG Hyphenation: updating for doc language it : English_US.pattern => Italian.pattern
07/23/19-17:00:04 DEBUG CreDocument: set hyphenation dictionary Italian.pattern
07/23/19-17:00:04 DEBUG CreDocument: set hyphenation left hyphen min 2
07/23/19-17:00:04 DEBUG CreDocument: set hyphenation right hyphen min 2
07/23/19-17:00:04 DEBUG CreDocument: set hyphenation trust soft hyphens 0
07/23/19-17:00:04 DEBUG CreDocument: rendering document...
CRE: document loaded, but styles re-init needed (possible epub with embedded fonts)
07/23/19-17:05:24 DEBUG CreDocument: rendering done.

Still requires just shy of 200MB of RAM, cache file is only slightly larger at 15MB.

SbAgOoTs · 07-23-2019, 12:53 PM

Mmmh, I hope Marinolino and somebody else makes a test too, because 10-15 min for the first opening would be acceptable.
Unfortunately on my phone after 3 hours no success and on the Aura One pretty the same...
And why other apps do it immediately?

07-22-2019, 12:35 PM	#1
SbAgOoTs Member Posts: 24 Karma: 10 Join Date: Sep 2014 Location: Italy Device: Kobo Aura One	KOReader doesn't open large, complex ebooks? 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 (https://download-a.akamaihd.net/file.../7d/nwt_E.epub ): never been able to open it, KOReader stays "thinking" forever... Any idea? It's really a bug? Bye

07-22-2019, 01:06 PM	#3
NiLuJe BLAM! Posts: 13,477 Karma: 26012492 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	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. Code: 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 ). Last edited by NiLuJe; 07-22-2019 at 01:19 PM.

07-22-2019, 01:24 PM	#5
NiLuJe BLAM! Posts: 13,477 Karma: 26012492 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	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. Last edited by NiLuJe; 07-22-2019 at 01:34 PM.

07-22-2019, 01:31 PM	#6
NiLuJe BLAM! Posts: 13,477 Karma: 26012492 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	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). Code: 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: Code: 07/22/19-19:33:23 DEBUG CreDocument: loading document... 07/22/19-19:33:28 DEBUG CreDocument: loading done. Last edited by NiLuJe; 07-22-2019 at 01:39 PM.

07-22-2019, 05:11 PM	#9
Marinolino Groupie Posts: 184 Karma: 2019866 Join Date: Feb 2018 Device: Kobo Aura-One (using KOReader app), Boox Note-3, iPad(s)	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. Last edited by Marinolino; 07-22-2019 at 05:45 PM.

07-22-2019, 12:45 PM	#2
NiLuJe BLAM! Posts: 13,477 Karma: 26012492 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	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.

07-22-2019, 01:18 PM	#4
SbAgOoTs Member Posts: 24 Karma: 10 Join Date: Sep 2014 Location: Italy Device: Kobo Aura One	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.

07-22-2019, 03:17 PM	#8
Frenzie Wizard Posts: 1,613 Karma: 724945 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	Fun fact: calibre took longer to open that than KOReader.

07-22-2019, 05:47 PM	#10
NiLuJe BLAM! Posts: 13,477 Karma: 26012492 Join Date: Jun 2010 Location: Paris, France Device: Kindle 2i, 3g, 4, 5w, PW, PW2, PW5; Kobo H2O, Forma, Elipsa, Sage, C2E	@Marinolino: Many thanks for that random drive-by testing on the exact same device! .

07-22-2019, 05:49 PM	#11
SbAgOoTs Member Posts: 24 Karma: 10 Join Date: Sep 2014 Location: Italy Device: Kobo Aura One	Very interesting. On both my devices (the Aura One and a Samsung Galaxy J4+) after 3 hours I'm still waiting to open it... The only difference being that I'm actually trying to open the Italian version of this book: maybe it has some problems (other ebook readers open it anyway), tomorrow I will try the English version too.

07-23-2019, 03:09 AM	#12
SbAgOoTs Member Posts: 24 Karma: 10 Join Date: Sep 2014 Location: Italy Device: Kobo Aura One	Hi guys, as expected: wrong test book... I confirm I can quickly open the English version I linked above as well, but I can't open (with KOReader only, other ebook readers/apps give no problems...) the Italian one: https://download-a.akamaihd.net/file.../f3/nwt_I.epub. Any idea? Bye

07-23-2019, 12:53 PM	#15
SbAgOoTs Member Posts: 24 Karma: 10 Join Date: Sep 2014 Location: Italy Device: Kobo Aura One	Mmmh, I hope Marinolino and somebody else makes a test too, because 10-15 min for the first opening would be acceptable. Unfortunately on my phone after 3 hours no success and on the Aura One pretty the same... And why other apps do it immediately?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Koreader in Aura H2O doesn't wake up	toodeeptofind	Kobo Developer's Corner	6	03-01-2018 02:47 PM
KOreader on Kobo Touch doesn't open an epub anymore...	sbaguz	KOReader	8	04-08-2017 01:53 PM
Koreader doesn't respond touch on Oasis	bingo619	KOReader	11	07-26-2016 05:28 PM
New KoReader update doesn't work in my device.	the_doc	KOReader	19	04-18-2016 03:10 PM
Koreader doesn't work on 5.4.3	vr4y	Kindle Developer's Corner	13	04-15-2014 03:40 AM

Advert

Advert