We are having several errors coming from Aspose throwing this message:
Aspose.Words.FileFormatUtil’ threw an exception. => Exception of type ‘System.OutOfMemoryException’ was thrown.
This is a business critical system - can you please advise as a matter of urgency?
aspose_cleanup_error.png (151.0 KB)
We are sorry for the inconvenience caused.
We are looking into this issue (WORDSCLOUD-619) and will update you with our findings soon.
In order to reproduce the issue on our end, we need the resource file. Please zip the input file and attach with this thread.
We have marked this thread private, only you and Aspose Staff have access to the thread.
I am unable to reproduce this problem right now - it seems that it happens randomly without any patterns on our side in relation to data or the template itself.
Thanks for sharing further information. We will perform random testing and stress testing on our end to reproduce the issue.
We are facing the same issue while taking use of npm package “asposestoragecloud”,
This issue happens when we make a call to download the file from storage thru “GetDownload” function.
The memory utilization and cpu utilization shoots up.
Moreover it is always advisable to pass back the downstream so that we need not buffer the complete file into memory rather just pass the same downstream to whatever place we want to save the file.
But there is only provision to pass a call back function which would return the complete file buffer once all of it is being downloaded into memory,
We are a paid member of your services and this issue is breaking our production and we had to roll back our release which is sad.
Plz work on this and let us know at the earliest.
Thanks
Thank You for bearing with us. We have been informed that the issue you are facing has been fixed. Kindly check your sue case again and let us know if you face any further issues.
Are your sure. The package was published 8 months back :
image.png (64.4 KB)
what has been fixed ?
Can you plz elaborate.
@abhisheknew - I am sorry I have gotten the support tickets mixed up. The issues for @aspose.heffron.au is fixed. Your issue is currently been worked on by our support team. I apologize for the mix up.
Any Update on this.
Both of the following issues will fix as we successfully integrate Aspose.Storage APIs into Aspose.Words Node.js SDK.
Unfortunately, it is a time-consuming task and we may not be able to release the updated Node.js SDK very soon.
P.S. Your issues are logged in our internal tracking software as WORDSCLOUD-621 and WORDSCLOUD-595.
When can we expect this release be rolled out?
Unfortunately, at present, we cannot give the time estimate but the integration of Aspose.Storage APIs in Aspose.Words Cloud SDK for Node.js is our highest priority.
Sure Thanks.
Please keep us posted whenever you guys are done with that.
Thanks
Thanks for your patience. Please note your above reported issue WORDSCLOUD-619 is fixed in V4 API Version. We are unable to reproduce the issue in new API version. At the same time we have increased the amount of memory in our V4 version containers.
Furthermore, please note we have also included storage APIs in Aspose.Words Cloud since V4 API Version. Now you can perform different storage related operations directly, without using a separate Cloud API for the purpose.