TOPIC:

Hi!
I wrote an app that calls "page.FindOpen(text, MATCH_CASE, WHOLE_WORD);" it works fine except for android N that crashes without possibility to catch exceptions.
What can I do?
Thanks

We have tested the latest version on Android N, and the search is working fine.

Can you replicate your issue with the demo project?
Can you share with us the steps to reproduce the issue?
Does it happen with certain documents? (if yes, can you please send us one)
If you were able to get the crash log, it will be very helpful.

It happens when i select all entire pdf page or when i select a row then i change page.
Here a crash log

---

beginning of crash
06-05 11:32:59.381 29029-29029/it.egeaonline.easybook A/libc: stack corruption detected
06-05 11:32:59.381 29029-29029/it.egeaonline.easybook A/libc: Fatal signal 6 (SIGABRT), code -6 in tid 29029 (online.easybook)

[ 06-05 11:32:59.386 372: 372 W/ ]
debuggerd: handling request: pid=29029 uid=10199 gid=10199 tid=29029
06-05 11:32:59.482 29363-29363/? A/DEBUG: *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
06-05 11:32:59.482 29363-29363/? A/DEBUG: Build fingerprint: 'google/bullhead/bullhead:7.1.2/N2G47O/3852959:user/release-keys'
06-05 11:32:59.482 29363-29363/? A/DEBUG: Revision: 'rev_1.0'
06-05 11:32:59.482 29363-29363/? A/DEBUG: ABI: 'arm64'
06-05 11:32:59.482 29363-29363/? A/DEBUG: pid: 29029, tid: 29029, name: online.easybook >>> it.egeaonline.easybook <<<
06-05 11:32:59.482 29363-29363/? A/DEBUG: signal 6 (SIGABRT), code -6 (SI_TKILL), fault addr

---

06-05 11:32:59.485 29363-29363/? A/DEBUG: Abort message: 'stack corruption detected'
06-05 11:32:59.485 29363-29363/? A/DEBUG: x0 0000000000000000 x1 0000000000007165 x2 0000000000000006 x3 0000000000000008
06-05 11:32:59.485 29363-29363/? A/DEBUG: x4 0000000000000000 x5 0080000000808080 x6 0000000000000000 x7 0000000000000010
06-05 11:32:59.485 29363-29363/? A/DEBUG: x8 0000000000000083 x9 ffffffffffffffdf x10 0000000000000000 x11 0000000000000001
06-05 11:32:59.485 29363-29363/? A/DEBUG: x12 0000000000000008 x13 0000000000000000 x14 0000000000000000 x15 0016b8999fe0e011
06-05 11:32:59.485 29363-29363/? A/DEBUG: x16 0000007333301ee0 x17 00000073332abb24 x18 0000000020000001 x19 0000007336588b40
06-05 11:32:59.485 29363-29363/? A/DEBUG: x20 0000000000000006 x21 0000007336588a98 x22 000000000000000b x23 000000000000007f
06-05 11:32:59.485 29363-29363/? A/DEBUG: x24 0000007ff4bfe86c x25 00000000000003cc x26 00000000000003cc x27 5adafe4b9e28d170
06-05 11:32:59.485 29363-29363/? A/DEBUG: x28 0000007ff4bfeb00 x29 0000007ff4bfe6c0 x30 00000073332a8f50
06-05 11:32:59.485 29363-29363/? A/DEBUG: sp 0000007ff4bfe6a0 pc 00000073332abb2c pstate 0000000060000000
06-05 11:32:59.516 29363-29363/? A/DEBUG: backtrace:
06-05 11:32:59.516 29363-29363/? A/DEBUG: #00 pc 000000000006bb2c /system/lib64/libc.so (tgkill+
06-05 11:32:59.516 29363-29363/? A/DEBUG: #01 pc 0000000000068f4c /system/lib64/libc.so (pthread_kill+64)
06-05 11:32:59.517 29363-29363/? A/DEBUG: #02 pc 0000000000023f58 /system/lib64/libc.so (raise+24)
06-05 11:32:59.517 29363-29363/? A/DEBUG: #03 pc 000000000001c810 /system/lib64/libc.so (abort+52)
06-05 11:32:59.517 29363-29363/? A/DEBUG: #04 pc 0000000000020f08 /system/lib64/libc.so (__libc_fatal+104)
06-05 11:32:59.517 29363-29363/? A/DEBUG: #05 pc 000000000006aa10 /system/lib64/libc.so (__stack_chk_fail+16)
06-05 11:32:59.517 29363-29363/? A/DEBUG: #06 pc 000000000005f068 /data/app/it.egeaonline.easybook-2/lib/arm64/librdpdf.so (Java_com_radaee_pdf_Page_findOpen+1376)
06-05 11:32:59.517 29363-29363/? A/DEBUG: #07 pc 00000000000dbd90 /system/lib64/libart.so (art_quick_generic_jni_trampoline+144)
06-05 11:32:59.517 29363-29363/? A/DEBUG: #08 pc 00000000000d2a68 /system/lib64/libart.so (art_quick_invoke_static_stub+600)
06-05 11:32:59.517 29363-29363/? A/DEBUG: #09 pc 00000000000df4b0 /system/lib64/libart.so (_ZN3art9ArtMethod6InvokeEPNS_6ThreadEPjjPNS_6JValueEPKc+256)
06-05 11:32:59.517 29363-29363/? A/DEBUG: #10 pc 000000000029084c /system/lib64/libart.so

It seems like you are using custom implementation (not the demo one), so we need more information to be able to replicate the issue and hence fix it..

Can you replicate your issue with the demo project?
Can you share with us a code snippet to reproduce the issue?
Does it happen with certain documents? (if yes, can you please send us one)