MobileRead Forums - View Single Post - [Device Plugin] Kobo Touch Extended Driver

davidfor · 03-19-2017, 09:37 AM

I can reproduced the crash with catalogues generated from my libraries on my Aura H2O, but the same one on my Glo HD and Touch works. With at least one of the catalogues, the device rebooted when I first tried opening the book, but was OK after the restart.

I can't see any reason for this other than the large number of ToC entries. When a kepub is first opened, a word count us done for each ToC entry in the database. It's possible that it is a sickel time out. But, I also have a stack log, which usually means crash in the code.

Anyway, I don't think it's a problem with the driver. The catalogues are possibly large and complex enough to exceed some limit in the kepub renderer. Though that doesn't really explain why I am seeing it on only one device.

03-19-2017, 09:37 AM	#1691
davidfor Grand Sorcerer Posts: 24,905 Karma: 47303824 Join Date: Jul 2011 Location: Sydney, Australia Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos	I can reproduced the crash with catalogues generated from my libraries on my Aura H2O, but the same one on my Glo HD and Touch works. With at least one of the catalogues, the device rebooted when I first tried opening the book, but was OK after the restart. I can't see any reason for this other than the large number of ToC entries. When a kepub is first opened, a word count us done for each ToC entry in the database. It's possible that it is a sickel time out. But, I also have a stack log, which usually means crash in the code. Anyway, I don't think it's a problem with the driver. The catalogues are possibly large and complex enough to exceed some limit in the kepub renderer. Though that doesn't really explain why I am seeing it on only one device.