We are facing issues of
com.aspose.slides.Presentation objects not getting garbage collected and hence blocking a huge amount of memory. This does not happen to all presentation objects that have been created, but to some. So unfortunately I cannot reproduce it.
After waiting several hours and performing multiple garbage collections, the
com.aspose.slides.Presentation objects still remain in memory, although they are not used anymore by my application.
Looking at the nearest GC roots, it always reveals the same:
grafik.png (12.3 KB)
com.aspose.slides.ag6 looks very suspicious. It contains a static Stack which is only accessible via methods that contain synchronized blocks. That’s why I assume this is built for multi-threaded purposes. This whole construct can clearly can lead to memory leaks if the stack content does not get removed with absolute certainty.
Please investigate and also tell me if there is a temporary workaround to clean up this static stack. If I knew what
ag6 was used for, it would maybe also help me to reproduce it.
Operating System: Windows 10
Aspose Slides Java 20.5