Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ANR] crash when selecting file browser #5020

Closed
arooni opened this issue May 10, 2019 · 14 comments

Comments

@arooni
Copy link

commented May 10, 2019

  • KOReader version: 2019.05
  • Device: kindle fire 10" tablet (android 5.6.x i think)

Issue

Open up koreader
Click file browser
Change folder (in my case tried to move to ~/downloads)
koreader crashes.

what's interesting is changing to other directories seems to work ok, but the crash seems random right now.

the koreader home directory is on internal storage.

Steps to reproduce

crash.log (if applicable)

I can't seem to find the crash log in the koreader directory

@pazos

This comment has been minimized.

Copy link
Contributor

commented May 11, 2019

I can't seem to find the crash log in the koreader directory

to report logs you need to install adb and copy here the result of the command adb logcat KOReader:I *:S

Most crashes are self-explainatory, but if you can't see anything weird try with adb logcat KOReader:I AndroidRuntime:E *:F

@arooni

This comment has been minimized.

Copy link
Author

commented May 21, 2019

OK:

So I opened the file browser and clicked file browser and then clicked around some different folders and after clicking a few times, the app just crashes. I don't seem to see a crash message in the logcat messages.

log.txt

@pazos

This comment has been minimized.

Copy link
Contributor

commented May 21, 2019

Nope, try with the 2nd option

@arooni

This comment has been minimized.

Copy link
Author

commented May 21, 2019

MiniArooni ~/Downloads/image_folder: adb logcat KOReader:I AndroidRuntime:E *:F

still can't seem to see where the error is: log.txt

@pazos

This comment has been minimized.

Copy link
Contributor

commented May 21, 2019

No error in logs. Maybe amazon has some weird stuff on ActivityManager that kills the program?.

Please do the following:

  1. start KOReader first (to avoid logging a bunch of s**t)
  2. type adb logcat -c to clear the log buffer
  3. type adb logcat KOReader:V and let it print messages until you manage to crash the application
  4. attach the log here.
@arooni

This comment has been minimized.

@pazos

This comment has been minimized.

Copy link
Contributor

commented May 22, 2019

Error seems unrelated: Application Not Responding because input dispatching timed out. I have no idea why but I can't reproduce it anywhere.

E/ActivityManager(  551): ANR in org.koreader.launcher (org.koreader.launcher/.MainActivity)
E/ActivityManager(  551): PID: 19493
E/ActivityManager(  551): Reason: Input dispatching timed out (Waiting to send non-key event because the touched window has not finished processing certain input events that were delivered to it over 500.0ms ago.  Wait queue length: 3.  Wait queue head age: 7886.8ms.)
@pazos pazos added bug and removed need more info labels May 22, 2019
@arooni

This comment has been minimized.

Copy link
Author

commented May 22, 2019

tragic. i had no issues with the previous monthly stable release. i think i'll try to revert to that for the time being.

@pazos pazos changed the title koreader crashes when selecting file browser on android [ANR] crash when selecting file browser Jun 12, 2019
@arooni

This comment has been minimized.

Copy link
Author

commented Jun 24, 2019

seems to happen also in the may release but working so far on the april release.

@pazos

This comment has been minimized.

Copy link
Contributor

commented Jun 25, 2019

@arooni: just to be sure, can you reproduce on a device other than kindle fire 10" tablet?

@arooni

This comment has been minimized.

Copy link
Author

commented Jun 25, 2019

@pazos: My only other android device is a pixel xl where I cannot reproduce the bug.

@pazos

This comment has been minimized.

Copy link
Contributor

commented Jun 25, 2019

Seems that Amazon likes to flag "not responding" more than other firmwares.

Here is an updated build after koreader/android-luajit-launcher#149, which includes some memory leak fixes: https://www.dropbox.com/s/ihhy8sei4vnb9ab/koreader-android-arm-linux-androideabi.apk?dl=0

You can try to reproduce your issue with that build (you need to delete yours first, signatures don't match) just to know it isn't already unintentionally fixed 😄 The same applies to your other issue #4996 (but that one is completely unrelated)

Timmings are difficult on Android, it seems...

@arooni

This comment has been minimized.

Copy link
Author

commented Jun 26, 2019

@pazos

This comment has been minimized.

Copy link
Contributor

commented Jul 4, 2019

Fixed in #5096

@pazos pazos closed this Jul 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.