We are currently using Aspose.Slides for .NET 4.0 (version 184.108.40.206), and we have come across an issue that was found in a memory dump that appears to be related to the Aspose.Slides assembly. In this memory dump, there is approximately 6.8gb worth of System.String objects. Of those objects, over 75% of them are a string that looks similar to the following:
The string grows in size over time, and there is a new instance of the string created each time the string grows. So, for instance, when a new “dupXX” value is appended to the string value, it would appear that a new instance of the string is created, rather than reusing the same string again. When running WinDbg commands to hunt down the string, I was able to locate the following stack by using the “!GCRoot” command to locate the usage of a single instance of the string in question:
-> 00000000a86cac88 Aspose.Slides.Pptx.GroupShapeEx
-> 00000000a86cadb0 Aspose.Slides.Pptx.ShapeExCollection
-> 00000000a86cadd8 System.Collections.ArrayList
-> 00000000bdc0ebe0 System.Object
-> 000000008201e5b0 Aspose.Slides.Pptx.GroupShapeEx
-> 000000008201e6d8 Aspose.Slides.Pptx.ShapeExCollection
-> 000000008201e700 System.Collections.ArrayList
-> 00000000820bdab0 System.Object
-> 0000000088f59520 Aspose.Slides.Pptx.AutoShapeEx
-> 0000000088f5a9c8 .
-> 0000000022b75648 .
-> 00000001544d8848 .
-> 00000001544d8880 System.String
Also of note is that there is only one root location found for every instance of the string that is noted in the memory dump. This alludes to the fact that a new instance of the string is being created, rather than having the instance reused.
This is causing a huge memory consumption issue for one of our clients, so I would appreciate someone taking a look at this ASAP. Please let me know if I can provide any additional details about this issue. I don’t have recreate steps, at this point, but I can provide any details from the memory dump that will help diagnose this.
I have observed your comments. I request you to please use Aspose.Slides latest version 17.3.0 on your end. If there is still an issue than please share source presentation with us, Also please share environment details with us so that we can further investigate to resolve the issue.