Microsoft Windows Phone 8.1 support ends (13 Jul 2017)

Microsoft has ended support for Windows Phone 8.1

Questions about Android development and PDF

Crash in native library

More
IP: 200.94.128.217 5 years 1 month ago - 5 years 1 month ago #15572 by jomart
Hello, Support.

We are using Radaee SDK 3.55, and we are getting signal crashes from Google Play Console about a native library, the stack trace is the following:

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR)

backtrace:  
#00  pc 000000000002d138  /data/app/com.xx.xx-1/split_config.armeabi_v7a.apk!lib/armeabi-v7a/librdpdf.so (offset 0x1b5000)
  
#00  pc 000000000004230b  /data/app/com.xx.xx-1/split_config.armeabi_v7a.apk!lib/armeabi-v7a/librdpdf.so (offset 0x1b5000)
  
#00  pc 00000000019d9c7b  /data/app/com.xx.xx-1/oat/arm/base.odex (offset 0x16d2000)


We have not been able to reproduce this bug, we only know that happens in Samsung devices:

Samsung Galaxy Tab S2 Android 7.0
Samsung Galaxy Tab S 10.5 Android 6.0

Can you help us?.

Any information is appreciated. Thank you.

 
Last edit: 5 years 1 month ago by jomart.
More
IP: 111.196.240.141 5 years 1 month ago - 5 years 1 month ago #15573 by radaee
Replied by radaee on topic Crash in native library
dear user:the information seems not helps.
but some tips may help you to locate issue:
1. we recommend you can run with arm64 libraries, arm64 has higher performance.
2. if the crash binding with special PDF file, please send us the PDF file.
3. if you still can't sure what issue, may you replace native library as: www.radaeetz.com/20210814_1_android.libs.zip
this library fixed some crashed issue binding with some special PDF file.
Last edit: 5 years 1 month ago by radaee.
More
IP: 200.94.128.217 5 years 1 month ago #15580 by jomart
Replied by jomart on topic Crash in native library
Hello, Support.

The information is from Google Play Console.

When we updated Radaee SDK to 3.55 in our app we take the jniLibs from your PDF sample too, if you recommend me to use other libraries, so the libraries from your PDF sample are wrong?, currently we are using the following jniLibs libraries:

arm64-v8a
armeabi
armeabi-v7a
mips
mips64
x86
x86_64

The jniLib library that is crashing is armeabi-v7a that is in your PDF sample too.
More
IP: 79.19.167.55 5 years 1 month ago #15581 by support
Replied by support on topic Crash in native library
It's weird that those devices are running a 32bit environment.
Which 3.55.x version are you using?

You say that "The jniLib library that is crashing is armeabi-v7a that is in your PDF sample too.", it means that you've the device in your hands and the crashing file.
May you provide more details and crash log?
May you provide the eventual crashing pdf file?
May you check this  play.google.com/store/apps/details?id=com.radaee.pdfmaster and say if it's working or crashing?
 
More
IP: 111.196.244.92 5 years 1 month ago - 5 years 1 month ago #15583 by radaee
Replied by radaee on topic Crash in native library
dear user:
first point:
armeabi
mips
mips64
are not supported by Android NDK any more.
so, you shall delete these libraries.
second point:
the native libraries are matched with JNI codes.
that mean, java codes of package "com.radaee.pdf" shall update to 3.60, otherwise app will be crashed.
Last edit: 5 years 1 month ago by radaee.
More
IP: 200.94.128.217 5 years 1 month ago #15584 by jomart
Replied by jomart on topic Crash in native library
We are using Radaee SDK 3.55.5.

My apologies, I meant that the jniLib library that is crashing is armeabi-v7a that we updated with the library that is in your PDF sample.

The information that we provide is from Google Play Console, we have not been able to reproduce this crash.
Time to create page: 0.429 seconds
Powered by Kunena Forum