Memory leak - trying to find unobfuscated class name

Aspose.Words Product Family
1

Hi,


We’re debugging memory leaks in our application. In your Aspose.Words assembly we keep seeing the class type “x66dd9eaee57cfba4.x7c1d47b289dfd9fa” on the managed heap (over 110,000+ instances) when we’re traversing memory dumps in WinDBG - can you tell me what the actual class name is please? Will help us track it back to our application.

We’ve a hunch that it’s to do with Fonts…

Regards,

Vin
2

Hi Vin,

A request to share the API name has been forwarded to our product team. We will update you as soon as we have any update on this.

Best Regards,

3

Hi Vin,

By the look of the obfuscated name it must be a pretty old version of Aspose.Words. We started using Eazfuscator some time ago and it has very different obfuscated names.

We do not have mappings from obfuscated names to unobfuscated for previous versions as we do not normally have such requests. If you want, you should try Aspose.Words on the latest version and then we can map it to an unobfuscated name.

It is quite normal for Aspose.Words to create many objects on the heap. Do you actually get a persistent leak picture? E.g. more and more memory is consumed by Aspose.Words with every document processed? This is very unlikely to be the case, especially for such large number of objects. What is the size of the document you are processing when you get 110K objects?

Please test with the latest version and share the details.