How should I handle PDFNet terminate?

The PDFNet terminate method is currently a no-op in the .NET Framework version of PDFNet, and it can be safely omitted.

PDFNet terminate is not a required method call for most of the Apryse 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).

Did you find this helpful?

Trial setup questions?

Ask experts on Discord

Need other help?

Contact Support

Pricing or product questions?

Contact Sales