Dennis Gorelik (![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
dennisgorelik) wrote2015-06-18 06:34 pm
dennisgorelik) wrote2015-06-18 06:34 pm
Entry tags:
Converting doc/docx/pdf/text to each other
Lots of applications need to load and convert document files of different formats into other formats or into text.
You would have think that there would be a good solution to it.
Unfortunately it's not the case.
Existing solutions are either for desktop only, or buggy or extremely expensive (~$10K/year).
I thought I found a solution - DevExpress Document Server library for $599.99
Unfortunately, after running for couple of weeks it crashed my service with StackOverflowException exception:
----
https://www.devexpress.com/Support/Center/Question/Details/T257097
To my regret, there is no simple workaround to avoid this exception with your document. Regarding the time frame for fixing this issue, it is difficult to provide any estimate in such cases.
----
So now I need to find a way to prevent my service from dying in case if some random document is fed into it.
Sigh.
You would have think that there would be a good solution to it.
Unfortunately it's not the case.
Existing solutions are either for desktop only, or buggy or extremely expensive (~$10K/year).
I thought I found a solution - DevExpress Document Server library for $599.99
Unfortunately, after running for couple of weeks it crashed my service with StackOverflowException exception:
----
https://www.devexpress.com/Support/Center/Question/Details/T257097
To my regret, there is no simple workaround to avoid this exception with your document. Regarding the time frame for fixing this issue, it is difficult to provide any estimate in such cases.
----
So now I need to find a way to prevent my service from dying in case if some random document is fed into it.
Sigh.
no subject
no subject
Are memory leaks and occasional fatal crashes pretty much guaranteed?
no subject
It mean skewered tables and garbage in some places instead of text.
> Are memory leaks and occasional fatal crashes pretty much guaranteed?
For a .NET library on a web server? Of course.
no subject
That's not a serious problem.
The crashes that kill the whole process - that's what concerns me.
> For a .NET library on a web server? Of course.
Do you mean any .NET library on a web server crash es occasionally?
Or such crashes are specific to conversion of DOC files (due to old COM storage calls)?
I'm not sure about Web Server, because IIS automatically recovers with problems (so we might have not noticed) but our windows service did not exit due to crash for several years (and when it did it was our silly coding mistake).