Hello,
We have been using the Aspose Total suite for a while now. The only thing we do with it is to convert office documents to PDF.
I’ve read through this forum on all the issues with memory consumption associated with the Words assembly. So I a well aware of the massive amounts of memory it uses to convert to PDF.
I just downloaded version 14.1.0.0 and I do see improvements.
However, I still have concerns with how long the memory is held after the conversion.
I’ve written a small application which gives visual representation of memory usage of the application while it is running. When I select a single ~3MB .doc file (no images or tables…just text), the app memory uses almost 200MB to convert (kind of expected). But after the conversion, memory usage seems to slowly climb another 30MB or so for about 6 or 7 min. before starting to release it.
I tried to attach a .zip of the project, but there seems to be some problem attaching it.
I would be very interested in your response.
Hi Steve,
Thanks for your inquiry. Please remove “Aspose.Words.dll” from your project’s “bin” directory to reduce the archieve size, zip your project again and attach it here for testing. You can also share your sample project via SkyDrive, DropBox or any free file sharing service. As soon as you send this simple application to us, we’ll start investigation into your issue and provide you more information.
Best regards,
Thank you for your response.
The attached project is designed to do conversions (one at a time) using the following Aspose assemblies:
- Words
- Slides
- Cells
- Pdf
As requested in your response, and required by the attachment warning, all assemblies and the license file has been removed from the project. So it will not compile as it is. You will need to add references to the above assemblies and use your own license file.
My main concern at this time is the behavior of Words after converting a .doc or .docx file.
Hi Steve,
Thanks for the additional information. Could you please also attach your sample .docx/.doc file, you’re getting this problem with here for testing. We will investigate the issue further on our end and provide you more information.
Best regards,
This problem is not specific to a single document. Using Words to convert any .doc or .docx to PDF shows the problem.
But, I will attach a sample .doc for you.
I zipped it up for a smaller attachment.
Hi Steve,
I tested the scenario and have managed to reproduce the same problem on my side. For the sake of correction, I have logged this problem in our issue tracking system as
WORDSNET-9803. Our development team will further look into the details of this problem and we will keep you updated on the status of correction. We apologize for your inconvenience.
Best regards,
Hi Steve,
Thanks for being patient. Regarding WORDSNET-9803, our development team has completed the work on your issue and has come to a conclusion that this issue and the undesired behaviour you’re observing is actually not a bug in Aspose.Words. So, we will close this issue as ‘Not a Bug’.
The problem occurs because of some issue with vshost.exe when running in “debug” mode (F5) command. The normal behavior can be observed if the compiled .exe is run separately or if the application is started from Visual Studio using “Start Without Debugging” (Ctrl+F5) command.
If we can help you with anything else, please feel free to ask.
Best regards,
Thank you for finding this. It does in fact let go of memory after use.
I guess I never tried running this test program outside of the Visual Studio.
I am satisfied with your findings.
Hi Steve,
Thanks for your feedback. In case you have further inquires or need any help, please let us know.
Best regards,