We were surprised by the memory use of the Aspose.Words product since we’re using it primarily for conversion.
We will try to work around this memory use (due to the DOM I suppose), but our concern is how we can protect our
existing application and process from low memory conditions.
For example, I would not want an OOM situation caused by the Aspose suite’s allocations to interfere with
memory allocation for other parts of our application (e.g. view generation, storage layer, etc) which might
result in unpredictable behaviour for our users.
Do you have a recommended or best practice approach?
Is there a way to get a callback on allocations so we can monitor memory use?
We can wrap the libraries in a separate JVM instance, but that’s rather “brute force”. I’d prefer something
within our existing process.