Book crashes Koreader on android but opens fine on Kobo

jlynton · 02-23-2022, 05:38 AM

I have two devices, both running KOReader 2022.01. There is one epub book that opens without problems on my Kobo Clara, but on my Inkpalm 5 (android) if I try to open the same book it crashes KOReader.

I have tried reformatting the book, checked it with epubcheck, cleared the cache etc. but it keeps on crashing. I would be grateful for any advice on how to troubleshoot this.

hius07 · 02-23-2022, 07:06 AM

Are you trying to open the book in landscape mode?
Try portrait mode. If it is okay, take the current nightly build or wait for 2022.02. The bug has been fixed.

jlynton · 02-23-2022, 07:25 AM

Quote:

Originally Posted by hius07

Are you trying to open the book in landscape mode?
Try portrait mode. If it is okay, take the current nightly build or wait for 2022.02. The bug has been fixed.

Thanks for the suggestion, but I have it in portrait mode. Other books open fine on the device.

pazos · 02-23-2022, 07:52 AM

From GH Bug report template: Android logs are kept in memory. Please go to Help → Bug Report to save these logs to a file.

Just do the steps needed to reproduce the crash.
After the crash follow instructions above and attach the crash.log file (its path is documented on the bug report widget).

Bugs reports are better reported on GH but if you attach the log here I can make a ticket for this.

Also there're some bugs that are old by definition and were already fixed in master. It is always recommended to try to reproduce the bug you find on last nightly before submitting a new ticket.

jlynton · 02-23-2022, 08:50 AM

Quote:

Originally Posted by pazos

From GH Bug report template: Android logs are kept in memory. Please go to Help → Bug Report to save these logs to a file.

Thanks pazos, but I cannot find Help - Bug report on my device.

hius07 · 02-23-2022, 09:07 AM

Top menu - Hamburger (rightmost) - Help - Report a bug

jlynton · 02-23-2022, 09:26 AM

Quote:

Originally Posted by hius07

Top menu - Hamburger (rightmost) - Help - Report a bug

Thanks, I hadn't realised it was in KOReader itself. Here's the log.

Frenzie · 02-23-2022, 03:34 PM

When was the crash exactly? I'm not seeing anything weird in there.

jlynton · 02-24-2022, 06:11 AM

Quote:

Originally Posted by Frenzie

When was the crash exactly? I'm not seeing anything weird in there.

It was shortly after 14:00 I believe. I am a bit short of time now, but will try to reproduce it later and upload another crash log.

Frenzie · 02-24-2022, 11:44 AM

It might be useful to enable debug logging while you're at it. From the file manager, tools → developer options → debug logging.

jlynton · 03-01-2022, 01:21 PM

Hello, and sorry for the delay in responding.
I was unable to find 'developer options', am now running KOReader 02.2022

I attach a new crash.log, if you go to 03-01 17:54:21.542 that is where I tried to open the book. I hope this is of help.

[edit] I have found and enabled debug logging, see newcrash.log.zip, tried to open the book at 03-01 18:53:35.712 [/edit]

Frenzie · 03-01-2022, 03:00 PM

There's something I didn't think to ask previously. Is it possible the book's just taking a really long time to load?

Although since we added this it should no longer happen that Android displays a not responding message if you tap on the screen while it's busy.
https://github.com/koreader/koreader...derui.lua#L110

pazos · 03-01-2022, 03:11 PM

Indeed. CRengine starts rendering the document and, after 30 seconds, the VM dies.

Code:

03-01 18:53:36.444 V/KOReader(14325):  CreDocument: rendering document...
03-01 18:54:04.068 I/zygote  (14325): Thread[3,tid=14331,WaitingInMainSignalCatcherLoop,Thread*=0xa5aa3200,peer=0x14240130,"Signal Catcher"]: reacting to signal 3
03-01 18:54:04.068 I/zygote  (14325): 
03-01 18:54:04.165 I/zygote  (14325): Wrote stack traces to '[tombstoned]'

Unfortunately there's no enough info to figure out what's happening. It could be an out of memory error or something else.

If you're able to get the tombstone then please attach it here too. If not you can enable ADB and dump the full logs android provides. Sadly apps cannot log system wide info, such as debug statements.

More info in https://source.android.com/devices/t...l=en#debuggerd

You can also attach the document here. If it is copyrighted you'll need to scramble it with a calibre plugin and check that you still get the error on the scrambled copy.

Just a few more questions: how many MB of ram has your device? Can you reproduce the issue in any other android device with a minimum of 1000MB of ram?

jlynton · 03-02-2022, 11:05 AM

Thank you both for your replies.

Frenzie, I did once try leaving it for 20 minutes to see if it would load, it did not.

pazos, I have no idea how to get the tombstone, is it a complicated procedure? my device is an Inkpalm 5 which has 1GB of ram. I have previously opened many books, some much larger (file size and/or number of pages) without any problems. Which calibre plugin can be used to scramble the book?

Frenzie · 03-02-2022, 12:56 PM

See https://www.mobileread.com/forums/sh...d.php?t=267998 for the ScrambleEbook plugin.

02-23-2022, 05:38 AM	#1
jlynton Evangelist Posts: 414 Karma: 216544 Join Date: Feb 2012 Device: Kobo Clara HD, Moaan Inkpalm 5.	Book crashes Koreader on android but opens fine on Kobo I have two devices, both running KOReader 2022.01. There is one epub book that opens without problems on my Kobo Clara, but on my Inkpalm 5 (android) if I try to open the same book it crashes KOReader. I have tried reformatting the book, checked it with epubcheck, cleared the cache etc. but it keeps on crashing. I would be grateful for any advice on how to troubleshoot this. Last edited by jlynton; 02-23-2022 at 05:39 AM. Reason: typo

03-01-2022, 03:11 PM	#13
pazos cosiñeiro Posts: 1,271 Karma: 2200049 Join Date: Apr 2014 Device: BQ Cervantes 4	Indeed. CRengine starts rendering the document and, after 30 seconds, the VM dies. Code: 03-01 18:53:36.444 V/KOReader(14325): CreDocument: rendering document... 03-01 18:54:04.068 I/zygote (14325): Thread[3,tid=14331,WaitingInMainSignalCatcherLoop,Thread*=0xa5aa3200,peer=0x14240130,"Signal Catcher"]: reacting to signal 3 03-01 18:54:04.068 I/zygote (14325): 03-01 18:54:04.165 I/zygote (14325): Wrote stack traces to '[tombstoned]' Unfortunately there's no enough info to figure out what's happening. It could be an out of memory error or something else. If you're able to get the tombstone then please attach it here too. If not you can enable ADB and dump the full logs android provides. Sadly apps cannot log system wide info, such as debug statements. More info in https://source.android.com/devices/t...l=en#debuggerd You can also attach the document here. If it is copyrighted you'll need to scramble it with a calibre plugin and check that you still get the error on the scrambled copy. Just a few more questions: how many MB of ram has your device? Can you reproduce the issue in any other android device with a minimum of 1000MB of ram?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
ePub book looks fine but misses pages on Kobo Aura ONE	jbmangan	Devices	14	10-10-2020 01:43 PM
KOReader bug - start filemanager opens book	hyurte	KOReader	6	09-26-2020 05:04 AM
How to let koreader on Android open the last book after startup ?	Norbi24	KOReader	3	09-14-2019 10:22 AM
Odd; Kobo-purchased book reads fine on Desktop, WiFi and Sony -but not on Kobo Touch.	beautifulsoup	Kobo Reader	4	07-17-2012 09:29 AM
kobo auto opens first book on screen	polli	Kobo Reader	8	03-08-2012 09:59 AM

02-23-2022, 07:06 AM	#2
hius07 Wizard Posts: 1,058 Karma: 3581267 Join Date: Sep 2014 Location: Ukraine Device: Kindle PW2, PW3, PW4, Voyage	Are you trying to open the book in landscape mode? Try portrait mode. If it is okay, take the current nightly build or wait for 2022.02. The bug has been fixed.

02-23-2022, 07:52 AM	#4
pazos cosiñeiro Posts: 1,271 Karma: 2200049 Join Date: Apr 2014 Device: BQ Cervantes 4	From GH Bug report template: Android logs are kept in memory. Please go to Help → Bug Report to save these logs to a file. Just do the steps needed to reproduce the crash. After the crash follow instructions above and attach the crash.log file (its path is documented on the bug report widget). Bugs reports are better reported on GH but if you attach the log here I can make a ticket for this. Also there're some bugs that are old by definition and were already fixed in master. It is always recommended to try to reproduce the bug you find on last nightly before submitting a new ticket.

02-23-2022, 09:07 AM	#6
hius07 Wizard Posts: 1,058 Karma: 3581267 Join Date: Sep 2014 Location: Ukraine Device: Kindle PW2, PW3, PW4, Voyage	Top menu - Hamburger (rightmost) - Help - Report a bug

02-23-2022, 03:34 PM	#8
Frenzie Wizard Posts: 1,619 Karma: 724945 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	When was the crash exactly? I'm not seeing anything weird in there.

02-24-2022, 11:44 AM	#10
Frenzie Wizard Posts: 1,619 Karma: 724945 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	It might be useful to enable debug logging while you're at it. From the file manager, tools → developer options → debug logging.

03-01-2022, 03:00 PM	#12
Frenzie Wizard Posts: 1,619 Karma: 724945 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	There's something I didn't think to ask previously. Is it possible the book's just taking a really long time to load? Although since we added this it should no longer happen that Android displays a not responding message if you tap on the screen while it's busy. https://github.com/koreader/koreader...derui.lua#L110

03-02-2022, 11:05 AM	#14
jlynton Evangelist Posts: 414 Karma: 216544 Join Date: Feb 2012 Device: Kobo Clara HD, Moaan Inkpalm 5.	Thank you both for your replies. Frenzie, I did once try leaving it for 20 minutes to see if it would load, it did not. pazos, I have no idea how to get the tombstone, is it a complicated procedure? my device is an Inkpalm 5 which has 1GB of ram. I have previously opened many books, some much larger (file size and/or number of pages) without any problems. Which calibre plugin can be used to scramble the book?

03-02-2022, 12:56 PM	#15
Frenzie Wizard Posts: 1,619 Karma: 724945 Join Date: Oct 2014 Location: Antwerp Device: Kobo Aura H2O	See https://www.mobileread.com/forums/sh...d.php?t=267998 for the ScrambleEbook plugin.

Advert

Advert