> For the complete documentation index, see [llms.txt](https://docs.apryse.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.apryse.com/core/get-started/faq/how-to-handle-terminate.md).

# How should I handle PDFNet terminate?

World's #1 PDF SDK Library for Web, Mobile, Server, Desktop

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.

{% hint style="warning" %}
**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.
{% endhint %}

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).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.apryse.com/core/get-started/faq/how-to-handle-terminate.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.