Platforms
Frameworks
Languages
Platform Specifics
File format support
The Apryse SDK in Node.js automatically cleans up all objects in memory when a process is initialized using PDFNet.runWithCleanup()
once the process has finished running. In almost all cases, it is recommended to use the PDFNet.runWithCleanup()
function to avoid memory leaks and complicated memory management.
For most situations, using PDFNet.runWithCleanup()
and [Obj].takeOwnership()
is sufficient for managing memory. However, there are additional ways to manage your memory usage:
In some situations you may wish to retain an object after the process has finished. A common example of this would be to create a document and retain it after processing. The ElementEdit sample on the samples page has an example of how this can be done.
[Obj].takeOwnership()
Deallocates individual objects. Only objects that derive from PDFNet.Destroyable have this method.
[Obj].destroy()
Stack-based deallocation. Calling endDeallocateStack()
will deallocate all objects that were created since the last call to PDFNet.startDeallocateStack()
. In general, stack-based deallocation is recommended because it is easier to manage for larger sections of code.
PDFNet.startDeallocateStack()
PDFNet.endDeallocateStack()
Here are some examples for the various deallocation options
Did you find this helpful?
Trial setup questions?
Ask experts on DiscordNeed other help?
Contact SupportPricing or product questions?
Contact Sales