Koreader not responding

[pbrouty]

After last update for May 2021.
Using Onyx boox Poke 2. When I turn off the screen while Koreader is open, and then turn it back on after about 20 seconds, Koreader doesn't respond to touches and will give an error message "Koreader not responding. Wait or Close"

[pazos]

Originally Posted by pbrouty

After last update for May 2021.
Using Onyx boox Poke 2. When I turn off the screen while Koreader is open, and then turn it back on after about 20 seconds, Koreader doesn't respond to touches and will give an error message "Koreader not responding. Wait or Close"

Try to reproduce the bug in the last nightly (link).

If you're using the F-droid version you need to uninstall the APK before install the new one.

If you can still reproduce the issue then:

1. Press close on the dialog.
2. Open the app again from your launcher
3. Go to Hamburguer menu -> Help -> Report a bug.

You'll see a message "attach log /path/to/log". Copy that file (it is always inside the koreader folder) here.

[pbrouty]

Originally Posted by pazos

Try to reproduce the bug in the last nightly (link).

If you're using the F-droid version you need to uninstall the APK before install the new one.

If you can still reproduce the issue then:

1. Press close on the dialog.
2. Open the app again from your launcher
3. Go to Hamburguer menu -> Help -> Report a bug.

You'll see a message "attach log /path/to/log". Copy that file (it is always inside the koreader folder) here.

Thank you. Attached is the log file.

[pazos]

Originally Posted by pbrouty

Thank you. Attached is the log file.

Thanks for the logs. You're the first crashlog reporter on android (The feature was added yesterday)


Sadly this isn't a "normal" ANR and I don't see anything relevant on logs.

The message

05-23 20:52:18.852 15569 15574 I reader.launche: Thread[2,tid=15574,WaitingInMainSignalCatcherLoop,Thread*=0xeb908000,peer=0x17140190,"Signal Catcher"]: reacting to signal 3

Is the VM reacting to SIGQUIT (which happens when you press "close" on the ANR dialog) but there's no reason there that could explain why android thinks the app is not responding.

I did notice there are a few seconds between the app is paused and the framework label it as not responding. That suggests an issue in ON_STOP. In that case reverting https://github.com/koreader/koreader/pull/7630 could work.

[pazos]

Does this version still crashes the same way?: https://www.dropbox.com/s/4zxi0wuxlp...-test.apk?dl=0

Please do the usual dance: uninstall APK, install new, confirm bug, attach log.

[pbrouty]

This version (test) is working. Thanks!

[NiLuJe]

@pazos: Re-reading the issue and what you said there about STOP, can we actually run Lua code after that event, or will Android say "nope, I'm freezing that activity", hence the potential ANR?

(Looking at the handlers, it's mostly I/O and task (un)scheduling, but code nonetheless ^^).

[pazos]

Originally Posted by NiLuJe

@pazos: Re-reading the issue and what you said there about STOP, can we actually run Lua code after that event, or will Android say "nope, I'm freezing that activity", hence the potential ANR?

(Looking at the handlers, it's mostly I/O and task (un)scheduling, but code nonetheless ^^).

The thread with the LuaJIT instance should be ready to execute chunks of lua when the activity is stopped. Anything network related or window related will fail when the activity isn't in the foreground.

Not very familiar with UIManager, but it looks that both "Suspend" and "Resume" are no-op in Android, so I guess we can remove them: https://github.com/koreader/koreader...ua#L1761-L1772.

If they're doing something we can broadcast them onResume/onPause instead onStart/onStop.

onStop callback isn't very reliable and most devices never reach that state unless we request an explicit destroy using finish()

[NiLuJe]

@pazos: The actual power event are no-ops, yeah (as in, we can't *trigger* a suspend, or *catch* say, a power button press that would have tripped one). But the "messaging" Events are platform-agnostic .

So yeah, moving them to resume/pause instead was also the best idea I could come up with ^^.

[pbrouty]

Will the fix be included in a future nightly build or in the next stable release?
Thanks for all your work on this great ereader.

[pazos]

Originally Posted by pbrouty

Will the fix be included in a future nightly build or in the next stable release?
Thanks for all your work on this great ereader.

Yup. Probably tomorrow nightly: https://github.com/koreader/koreader/pull/7753. You'll need to uninstall the test APK before installing the official one.

Please give feedback because that bug cannot be reproduced outside Onyx Boox and the workaround is slightly different than the test version you tried.

[pbrouty]

OK, thanks. I know what you mean. I did not receive this error on my other two android devices (Lenovo tablet, Xiaomi phone); only on my Onyx Boox (which is my primary reader).
Thanks again for your work. I'll report back after giving it a test run.

[pbrouty]

I installed the latest nightly (47) and it's working well on the Poke 2. Thanks

[pazos]

Originally Posted by pbrouty

I installed the latest nightly (47) and it's working well on the Poke 2. Thanks

Great!. Thanks for the feedback

[Winkelschraube]

The problem still exists on 2021.05-85.

Onyx Poke2

Edit: Also on 2021.05-90. Crash after sleep.