Free Support Forum - aspose.com

OutOfMemoryError on OLEFormat.save()

Hi,

I got OutOfMemoryErrors for some documents if I try to save the content of an OLE object.

java.lang.OutOfMemoryError: Java heap space
at com.aspose.words.aw.e(Unknown Source)
at com.aspose.words.aw.save(Unknown Source)
at com.aspose.words.OleFormat.save(Unknown Source)
at com.aspose.words.OleFormat.save(Unknown Source)
at TestOutOfMemoryError$1.visitShapeStart(TestOutOfMemoryError.java:42)
at com.aspose.words.Shape.accept(Unknown Source)
at com.aspose.words.CompositeNode.acceptChildren(Unknown Source)
at com.aspose.words.Paragraph.accept(Unknown Source)
at com.aspose.words.CompositeNode.acceptChildren(Unknown Source)
at com.aspose.words.Body.accept(Unknown Source)
at com.aspose.words.CompositeNode.acceptChildren(Unknown Source)
at com.aspose.words.Section.accept(Unknown Source)
at com.aspose.words.CompositeNode.acceptChildren(Unknown Source)
at com.aspose.words.Document.accept(Unknown Source)
at TestOutOfMemoryError.testOutOfMemoryError(TestOutOfMemoryError.java:31)

And the size of the files is not big enough to explain the exception.
I attached a simple test case to reproduce the exception.

Stephan.


Hi

Thanks for your report. I have reproduced this bug using .NET version of Aspose.Words and logged it to our defect base as issue # 3711. We will try to fix it in one of our future releases. A notification will be posted here in this thread as soon as it will be done.

Best regards.

Is there any progress? Almost two months without any news?!

Do a release date exist for the next release of Words for Java?

Sorry for the delay.

You can try to workaround. It is probably a particular object that does not export well. If you can identify which object it is, you can then check for its ProgID and skip it during export.

I will look at this in the .NET version (it was probably fixed in the upcoming release). But it will take a few more weeks before we make next Java release.