MobileRead Forums - View Single Post - Book crashes Koreader on android but opens fine on Kobo

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?

03-01-2022, 03:11 PM	#13
pazos cosiñeiro Posts: 1,406 Karma: 2451781 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?