See attachment please, cannot post the text here
Can reproduce the problem on the localhost now. Have the html code causing this but cannot put it out in this forum. Where can I mail it?
I have e-mailed my contact info to you. Please note however that all user attachments on this forums are private. They can be downloaded only by the author of the post or members of Aspose.Words team. So you can safely attach them here as well.
You should have an e-mail now. Also attached here
I am afraid that this info is not sufficient to reproduce the error. Can you provide some files and html snippets that we can test and look for memory leaks?
The most interesting question is whether memory is leaking gradually or is quickly spent up in one particular document generating session. In the former case the problem will probably need to be solved by improving your web application code. In the latter, the problem most probably needs to be fixed in Aspose.Words itself.
I would also like to recommend you to use process recycling to prevent periodic memory leaks.
Try to google for "ASP.NET" "memory leaks". There are a lot of articles on how to monitor ASP.NET applications and prevent the failures.
Best regards,
Here some performance information
And some html code
Thanks for providing the additional info. I have reproduced the problem by calling DocumentBuilder.InsertHtml with the provided html text on an empty document. It is now logged to our defect base as issue #1468. We will try to fix it by the time of the next release in 2-3 weeks.
Best regards,
Any workaround you could think of for the moment?
Please hold on. We are trying to find if any temporary workaround is possible.
Any news on this one, would need a fix or workarund since this is a quite radical error…
I am afraid we have not fixed it yet. We will try to fix it in the next release, which we plan to publish in two weeks. I will give this issue a higher priority just to make sure it gets fixed as soon as possible.
Best regards,
I'm working on this now. You have the following HTML in the string:
I guess the span for one million columns causes quite a long delay and possibly out of memory too. If you can fix that in your HTML, you will be able to proceed. In the meantime we will put some sort of a guard against it.
Fixed in Aspose.Words 4.2.