We find that Aspose.PDF leaks memory in production, but it is impossible to debug due to the obfuscation when viewing memory profiler snapshots.
In the following reduced example using Aspose.Pdf 25.6.1, there is a spike…...are afraid that the earlier logged ticket has not been resolved...depends on the number of issues logged ahead of it and the complexity...