Some test text!
In order to achieve smoother viewing experience,
PDFViewCtrl keeps certain amount of invisible content. However, keeping invisible content increases memory usage. Android sets an upper bound on the VM heap size allowed for an app. By default,
PDFViewCtrl is set to use a quarter of maximum VM heap size for keeping visible and invisible content. Based on the memory footprint of your app, you may want to customize it.
To customize the memory usage:
pdfViewCtrl is an instance of
PDFViewCtrlwill not keep any invisible content.
setRenderedContentCacheSize(long)only controls the memory usage of VM heap size by
PDFViewCtrl, but not the native memory that
We are experiencing a lot of out of memory errors when rotating the device multiple times. Since the Activity is destroyed while rotating, we get a new (quite heavy) PDFViewCtrl every time we rotate the device.
PDFViewCtrl can handle rotation properly, it is recommended that you configure your activity to handle configuration changes. This way the view will not be recreated and it will be resized accordingly.
In your app
AndroidManifest.xml file, add
android:configChanges to your
<activity android:configChanges="keyboardHidden|orientation|screenSize|screenLayout|smallestScreenSize" > </activity>
onConfigurationChanged() in your activity:
mPdfViewCtrl is an instance of
On Android 3.0 and above, you can also increase the allowed heap size of an app.
In your app
AndroidManifest.xml file, add the
android:largeHeap="true" attribute to the
<?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" > <application android:largeHeap="true" > </application> </manifest>