在Android 8.0上运行时,应用崩溃(PDFViewer活动)

时间:2019-01-16 09:06:53

标签: android android-8.0-oreo mupdf android-pdf-api

我有一个应用程序可以在具有Android 7.1.1的设备上正常运行,但是在Android 8.0上崩溃,该活动是使用MuPdf库的pdf查看器。 这是崩溃日志:

                --------- beginning of crash
            2019-01-16 09:54:42.333 7703-7812/com.niveales.wind A/libc: Fatal signal 11 (SIGSEGV), code 2, fault addr 0xa5353a50 in tid 7812 (AsyncTask #5), pid 7703 (m.niveales.wind)
            2019-01-16 09:54:42.506 7815-7815/? I/crash_dump32: obtaining output fd from tombstoned, type: kDebuggerdTombstone
            2019-01-16 09:54:42.515 1511-1511/? I//system/bin/tombstoned: received crash request for pid 7703
            2019-01-16 09:54:42.518 7815-7815/? I/crash_dump32: performing dump of process 7703 (target tid = 7812)
            2019-01-16 09:54:42.522 7815-7815/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
            2019-01-16 09:54:42.525 7815-7815/? A/DEBUG: Build fingerprint: 'google/sdk_gphone_x86/generic_x86:8.1.0/OSM1.180201.007/4586646:user/release-keys'
            2019-01-16 09:54:42.525 7815-7815/? A/DEBUG: Revision: '0'
            2019-01-16 09:54:42.525 7815-7815/? A/DEBUG: ABI: 'x86'
            2019-01-16 09:54:42.525 7815-7815/? A/DEBUG: pid: 7703, tid: 7812, name: AsyncTask #5  >>> com.niveales.wind <<<
            2019-01-16 09:54:42.525 7815-7815/? A/DEBUG: signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xa5353a50
            2019-01-16 09:54:42.525 7815-7815/? A/DEBUG:     eax a5353a48  ebx 85bcadf8  ecx 886bf800  edx 00000000
            2019-01-16 09:54:42.525 7815-7815/? A/DEBUG:     esi 864ffcc0  edi 8927d174
            2019-01-16 09:54:42.525 7815-7815/? A/DEBUG:     xcs 00000073  xds 0000007b  xes 0000007b  xfs 0000003b  xss 0000007b
            2019-01-16 09:54:42.525 7815-7815/? A/DEBUG:     eip 84acab2a  ebp a54b7d00  esp 8927cfb0  flags 00210286
            2019-01-16 09:54:42.530 7815-7815/? A/DEBUG: backtrace:
            2019-01-16 09:54:42.531 7815-7815/? A/DEBUG:     #00 pc 00144b2a  /data/app/com.niveales.wind-FeG_C6JSXm9M1nvufPfB9Q==/lib/x86/libmupdf.so
            2019-01-16 09:54:42.532 7815-7815/? A/DEBUG:     #01 pc 001454ba  /data/app/com.niveales.wind-FeG_C6JSXm9M1nvufPfB9Q==/lib/x86/libmupdf.so (pdf_process_contents+490)
            2019-01-16 09:54:42.532 7815-7815/? A/DEBUG:     #02 pc 000e024d  /data/app/com.niveales.wind-FeG_C6JSXm9M1nvufPfB9Q==/lib/x86/libmupdf.so
            2019-01-16 09:54:42.532 7815-7815/? A/DEBUG:     #03 pc 000e0545  /data/app/com.niveales.wind-FeG_C6JSXm9M1nvufPfB9Q==/lib/x86/libmupdf.so (pdf_run_page_contents+261)
            2019-01-16 09:54:42.533 7815-7815/? A/DEBUG:     #04 pc 00046d1d  /data/app/com.niveales.wind-FeG_C6JSXm9M1nvufPfB9Q==/lib/x86/libmupdf.so (fz_run_page_contents+173)
            2019-01-16 09:54:42.533 7815-7815/? A/DEBUG:     #05 pc 00038487  /data/app/com.niveales.wind-FeG_C6JSXm9M1nvufPfB9Q==/lib/x86/libmupdf.so (Java_com_artifex_mupdfdemo_MuPDFCore_drawPage+2087)
            2019-01-16 09:54:42.533 7815-7815/? A/DEBUG:     #06 pc 0002b36f  /data/app/com.niveales.wind-FeG_C6JSXm9M1nvufPfB9Q==/oat/x86/base.odex (offset 0x2b000)
            2019-01-16 09:54:42.533 7815-7815/? A/DEBUG:     #07 pc 003251ff  [anon:libc_malloc:89280000]
            2019-01-16 09:54:42.534 7815-7815/? A/DEBUG:     #08 pc 002406a7  /dev/ashmem/dalvik-main space (region space) (deleted)
            2019-01-16 09:54:42.534 7815-7815/? A/DEBUG:     #09 pc 6864d98d  <unknown>
            2019-01-16 09:54:42.534 7815-7815/? A/DEBUG:     #10 pc 0c77ffff  /dev/ashmem/dalvik-main space (region space) (deleted) (offset 0xc80000)
            2019-01-16 09:54:42.535 7815-7815/? A/DEBUG:     #11 pc 0c77ffff  /dev/ashmem/dalvik-main space (region space) (deleted) (offset 0xc80000)
            2019-01-16 09:54:43.705 1511-1511/? E//system/bin/tombstoned: Tombstone written to: /data/tombstones/tombstone_05

知道如何解决此问题吗?

0 个答案:

没有答案