We're sorry Aspose doesn't work properply without JavaScript enabled.

Free Support Forum - aspose.com

Memory leakage in Aspose.Words

The memory may not be released until you close the application.

This is an admission you have a memory leak, you should fix it and/or expose dispose methods on your libraries.

1 Like


Thanks for your inquiry. Aspose.Words has some internal static objects which remain live after GC.Collect() because these static fields are GC roots. If you replace a call to Aspose.Words with a call to a class that has static members, you will see the same issue.

We’re observing leaks in a windows service processing thousands of documents per day using Aspose Words v16.4. The amount of memory being leaked couldn’t possibly be due to memory occupied by references to static variables.

1 Like


Thanks for your inquiry. To ensure a timely and accurate response, please attach the following resources here for testing:

  • Your input Word documents.
  • Please create a standalone console application ( source code without compilation errors ) that helps us to reproduce your problem on our end and attach it here for testing.

As soon as you get these pieces of information ready, we will start investigation into your issue and provide you more information. Thanks for your cooperation.

PS: To attach these resources, please zip and upload them.

A post was split to a new topic: Improve Memory Optimization | Memory Performance | Avoid Memory Leak & OutOfMemory Exceptions | Convert Word to PDF C# .NET