TOPIC:

Hi support,

A device with Android 5.0.2 that is using RadaeePDF 3.55 after paginate some pages is crashing due to memory problems, the UI is blocking and then close the app. We found that your sample app has defined a minSdkVersion 14 (Android 4.0) in the build.gradle.

The attached image shows the stack trace of the crash.

Can you help us to figure out what the problem is?, please.

Thank you in advance.

the OOM appears when emeory is not enough.
you can send the device information here.
and set Global.debug_mode = true; if you want trace memory information.

also, you may sent our sample PDF file, if it is relate to special PDF file.

The device information is the following:  

5.0.2 Galaxy Note Pro
Device
Brand:Samsung
Model:Galaxy Note Pro 12.2
Operating System
Version:5.0.2
Ram Memory: 3 GB
Internal Memory: 32 GB

It is not related to special PDF file. Our app uses RadaeePDF 3.55, when user is paginating suddenly the UI is blocking and the app closes, We checked your PDFSample app to know if this happens because of the android version of the device, but your PDFSample app has a minSdkVersion 14.

Can you help us?.

Thank you in advance.

minSdkVersion 14 is Android 4.0
this shall not prevent to install demo project on your device (5.0.2).
if our demo project has no this issue, the issue shall be integrate problems.

for example,
too many PDFLayoutView opened in one time,
or PDFLayoutView never close, when you are destroy activity.
or com.radaee.pdf package and native libraries are not match in same version.

Hello, Support.

We opened one PDFLayoutView at a time.
When the view is destroyed, the PDF is close too.
We updated the native libraries too.

This is happening with the last SDK version that we are using, this SDK is an update from 3.15.1 to 3.55.5. We would like to know if there were changes about memory management, the problem is with a device that has Android 5.0.2, but we checked the memory usage of a device that has Android 9 in the memory profiler from Android Studio, and we checked that Bitmap objects are the first object that is consuming a lot of memory. This is normal, or we need to do some changes in this SDK version?.

Any information is appreciated.
Thank you.

Is the memory consumption related to the pdf page size? To some special pdf file ? Or is it common to each pdf files?