> It mean skewered tables and garbage in some places instead of text.
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).
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png)
timeasmymeasure
no subject
Date: 2015-06-19 07:21 pm (UTC)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).