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
Crashes; Oreo 8.1, MuPDF related (crashes aswell) #299
Comments
I've got crashes too, running Samsung Android 8 on Galaxy S7 Intl: the document is shown perfectly, a while after I close it I get the message "Stopped working" which means it crashed. I think it's possibly a leak somewhere, if I find the time I will try to get a logcat |
Same problem here, Android 8.1 on Motorola Moto G5 Plus. |
Do you mean it happens on every pdf or a particular pdf?
How can one reproduce the crash?
|
Reproduce the crash? Just use the app LoL! It just crashes. Notice all of us reporting crashes are running Android 8.1 (AEX5.7 Zuk Z2 Pro here). Workaround for me is to open and close window before opening another document, either this or crash. Cheers fellows :-) |
Getting error while trying to open pdf. and app is crashing. E/Document Viewer.LibraryLoader: Native library cannot be loaded: Any one tell me how to resolve this error. |
I think I have found a solution: Can you confirm that this solves the crash issue for you as well? I think Android 8,9,10 are affected, but now with this simple change, it works without any crashes... |
Thanks for pinpointing hwasiti. Got another crash briefly after changing the Pages in Memory setting but its running normally now. Thanks a lot. :-) |
Glad it helped. I will do a pull request for the changes. And hopefully the developers will release newer version to playstore with different default value to correct the issue for everybody. It seems from my glance on playstore reviews today, there are a lot of bad reviews in 2018-2019 due to this crash. Before that in 2016 and 2017, average reviews were much better. |
I experienced crashes of 2.8.1 on Android 9 (Lineage). After swithing document viewer to background by opening another application it took some seconds until the os reported that d.v. was crashed. I found a workaround by switching battery optimization (I do not know whether this is the correct translation of the German menu item) off for document viewer. I hope this will not result in high energy consumption. |
@hwasiti Thanks for the If I understand correctly, the call stack looks like
which calls the C function fz_drop_display_list() in which a call to fz_defer_reap_start() was invoked. However, the latest code in MuPDFhttps://git.ghostscript.com/?p=mupdf.git;a=blob;f=fitz/dev_list.c;hb=f85653219a85a9f91cb14471485611ca5f6b25ba#l628 does not contain a call to fz_defer_reap_start() . The function is not found in the current code of MuPDF.
|
Tested versions 2.7.9 (armeabi-v7a and arm64-v8a) to 2.8.1 (arm64-v8a).
Application works normally when opening PDF documents via system file explorer. However, if I press the upper left back button to go to file explorer the app can crash, no matter if in bookcase or list view.
If I open the app via app drawer I can access configuration menu and etc. Once I open a document there in its file explorer and switch to another task via recents the app can crash.
If I open a PDF file via system file exporer app behaves normally until I start switching tasks via recents, then it can crash.
When I mean crash, I mean I get a system popup window which tells me “Document Viewer has stopped”.
I have “Show all ANRs” (show App Not Responding dialog for background apps) enabled in developer options.
Briefly tried MuPDF, crashing behaviour too. MuPDF and this app seem to share code.
Cheers :-)
The text was updated successfully, but these errors were encountered: