Some test text!

How should I handle PDFNet terminate"?

How should I handle PDFNet terminate?

PDFNet terminate is not a required method call for most of the PDFTron SDK. It should only be called optionally after all other PDFNet methods. The terminate should also only be called once before ending the application.

Only call terminate once
The terminate method will destroy required parts of PDFNet which are not designed to be restarted even with the initialize method.

The main reason PDFNet terminate exists is to clean up some resources which would be mistakenly reported as memory leaks in memory tracking applications (such as Purify or BoundsChecker etc).

Get the answers you need: Support

UPCOMING WEBINAR: "2021 in review: Top five new & updated features" Dec 9th @ 11am PT