Consistent crash on opening - cover problem?

[Uncle Robin]

KOReader has started crashing every time I open a new book. So far, I've been able to get past the crash by trying a few times and if necessary powering off and back on again. I took a photo of the most recent one, am I right in thinking it might be a problem with the cover images?

[Frenzie]

I think we'd need to see a bit more from the actual crash.log and perhaps a scrambled copy to say more. It looks like the log is cut off here?

[Uncle Robin]

Originally Posted by Frenzie

I think we'd need to see a bit more from the actual crash.log and perhaps a scrambled copy to say more. It looks like the log is cut off here?

Nothing secret or sensitive, they've all been books I recently downloaded from Kobo and de-drmd. I'll definitely post the log next time it happens. I just took a quick screenshot before that screen disappeared - it then goes back to the last book opened before the crash.

[Uncle Robin]

Here's the crash log - it seems to be "cannot register" a whole set of Noto fonts. Would removing them from the device stop the crashes?

[Frenzie]

No, that's harmless.

But this is the part that was cut off:

04/03/22-00:06:10 INFO  Kobo suspend: asked the kernel to put subsystems to standby, ret: true
./luajit: frontend/ui/uimanager.lua:1826: allowing standby that isn't prevented; you have an allow/prevent mismatch somewhere
stack traceback:
	[C]: in function 'assert'
	frontend/ui/uimanager.lua:1826: in function 'allowStandby'
	plugins/coverbrowser.koplugin/bookinfomanager.lua:643: in function 'collectSubprocesses'
	plugins/coverbrowser.koplugin/bookinfomanager.lua:743: in function 'action'
	frontend/ui/uimanager.lua:1210: in function '_checkTasks'
	frontend/ui/uimanager.lua:1631: in function 'handleInput'
	frontend/ui/uimanager.lua:1743: in function 'run'
	./reader.lua:291: in main chunk
	[C]: at 0x000140bd
!!!!
Uh oh, something went awry... (Crash n°1: 04/03/22 @ 00:06:16)
Running FW 4.30.18838 on Linux 4.9.56 (#337 SMP PREEMPT Thu Jan 13 14:23:14 CST 2022)
Attempting to restart KOReader . . .
!!!!

[Uncle Robin]

Whatever the "allow/prevent mismatch" is, how do I fix it?It's happening pretty consistently with every new book I open - I thin of the last 10 books I have opened, one surprised me by not crashing in this manner.

[NiLuJe]

Are you running a nightly with a standby timeout set? (if so, at which amount).

[NiLuJe]

This patch will allow us to see who's calling prevent/allow, which should help tracking down the misbehaving code...

diff --git a/frontend/ui/uimanager.lua b/frontend/ui/uimanager.lua
index 3a0cb8860..6acd3748b 100644
--- a/frontend/ui/uimanager.lua
+++ b/frontend/ui/uimanager.lua
@@ -1823,6 +1823,7 @@ Called once we're done with whatever we were doing in the background.
 Standby is re-enabled only after all issued prevents are paired with allowStandby for each one.
 ]]
 function UIManager:allowStandby()
+    logger.dbg("UIManager:allowStandby:", debug.traceback())
     assert(self._prevent_standby_count > 0, "allowing standby that isn't prevented; you have an allow/prevent mismatch somewhere")
     self._prevent_standby_count = self._prevent_standby_count - 1
 end
@@ -1833,6 +1834,7 @@ Prevent standby.
 i.e., something is happening in background, yet UI may tick.
 ]]
 function UIManager:preventStandby()
+    logger.dbg("UIManager:preventStandby:", debug.traceback())
     self._prevent_standby_count = self._prevent_standby_count + 1
 end

[NiLuJe]

See also https://github.com/koreader/koreader/pull/8962

[zwim]

@Uncle Robin
Could you please post your settings file here?
You find it under `/mnt/onboard/.adds/koreader/settings.reader.lua`

[Uncle Robin]

Here's a screenshot of my KOReader settings. I do run nightlies, but if I understand this screen properly, I have no standby set.

Please forgive my utter ignorance, but how do I add that code to my KOReader?

[zwim]

Thanks, for the screenshot.

I want to ask you for two things. It is important to do this in the correct sequence.

1.) Go to filemanager -> Tools -> More tools -> Developer options:
Enable debug logging and enable verbose debug logging.
Then wait for the crash and post the crash.log here. If there is no crash, please play a few minutes with KOReader and post the crash.log.

2.) Try to enable `Autostandby timeout` to something like 5 seconds.
If there is a crash please post the appropriate crash.log here or tell us if there is no crash.

[NiLuJe]

Unzip the following archive in the `.adds/koreader` folder.

And while you're rooting around in there, we might actually need the full `settings.reader.lua` file as-is, as @zwim requested above .

EDIT: You might want to restart KOReader after @zwim's step 1 above, too.

[Uncle Robin]

Here's the settings.reader.lua , extension changed to txt to allow it to be attached here. This is from prior to enabling the standby and verbose logging. I have enabled the logging am now going to set the 5 second standby as suggested and extract the pr8962 as suggested. Morituri te salutant!

[zwim]

Who will be so pessimistic. Morituri and so on .... tststststs ....

The settings.reader.lua look like it should be. I have the same device as you. Here it works, so we will get it soon.