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
Comments
to report logs you need to install adb and copy here the result of the command Most crashes are self-explainatory, but if you can't see anything weird try with |
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. |
Nope, try with the 2nd option |
still can't seem to see where the error is: log.txt |
No error in logs. Maybe amazon has some weird stuff on ActivityManager that kills the program?. Please do the following:
|
Error seems unrelated: Application Not Responding because input dispatching timed out. I have no idea why but I can't reproduce it anywhere.
|
tragic. i had no issues with the previous monthly stable release. i think i'll try to revert to that for the time being. |
seems to happen also in the may release but working so far on the april release. |
@arooni: just to be sure, can you reproduce on a device other than kindle fire 10" tablet? |
@pazos: My only other android device is a pixel xl where I cannot reproduce the bug. |
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... |
Just installed it and playing around with it initially it seems like there
are *no more crashes* when selecting the file browser, navigating to other
directories, etc.
Amazing! thanks for your help!
I did notice that when I use the square button to switch apps to another
app and come back to koreader, (i think this is issue #4996) that it clips
off the bottom of the screen for the menu bar as before.
may today be the best day of your life,
-------
david parkinson
founder - aroonilabs.com
blog - davidparkinson.com <https://www.davidparkinson.com/>
twitter - @followdavid <https://twitter.com/followdavid>
…On Tue, Jun 25, 2019 at 6:25 PM Martín Fernández ***@***.***> wrote:
Seems that Amazon likes to flag "not responding" more than other firmwares.
Here is an updated build after koreader/android-luajit-launcher#149
<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
<#4996> (but that one is
completely unrelated)
Timmings are difficult on Android, it seems...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#5020?email_source=notifications&email_token=AAEH465HTASAC6AVECA62TDP4KSNJA5CNFSM4HL64CO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODYR3ZIQ#issuecomment-505658530>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAEH46YNB4OHTMPVKKVA7V3P4KSNJANCNFSM4HL64COQ>
.
|
Fixed in #5096 |
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
The text was updated successfully, but these errors were encountered: