TOPIC:

In our application, we are using the PDFViewPager class and are seeing some memory issues. We followed your design pattern from PDFPagerAct, but the memory usage in the Native memory stack grows every time you swipe to a new page. What settings need to be configured to make sure that memory is not leaking via JNI libraries?

In addition, several lines are commented out in the PDFViewPager class. Of particular interest is VPage's SetConfigure method. How is this method intended to be used? What effect does it have? Finally, how are the values CLIP_W and CLIP_H intended to be used, as they aren't defined anywhere else in the class. Thank you.

Daniel
The Washington Post

You need to make sure that while navigating you are closing the unneeded pages (i.e. PDFPageAdapter.destroyItem is called) and setting ViewPager.setOffscreenPageLimit according to your needs.

Lines commented, belongs to non-implemented listeners, test codes or old codes..
VPage's SetConfigure --> old method that is replaced now with VPageRenderResult and blocks management. (zoom handling)