Hi we have upgraded EO.PDF component to version 5.0.34.2 and since we deployed it in our final release on customer environment customer getting this type of error:
FAIL: Convertion failed.
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that
other memory is corrupt.
at EO.Pdf.Internal.dc.d.Invoke(IntPtr A_0, String A_1)
at EO.Pdf.Internal.dc.c(IntPtr A_0)
at EO.Pdf.Internal.dc.a(g A_0, Int32 A_1, Int32 A_2, Int32 A_3)
at EO.Pdf.Internal.dc.n.Invoke(IntPtr A_0, String A_1, String A_2, Boolean A_3)
at EO.Pdf.Internal.dc.a(String A_0, Boolean A_1, Byte[] A_2)
at EO.Pdf.Internal.dc.a(String A_0, Boolean A_1, Boolean A_2, Int32 A_3, t A_4, String[] A_5, Byte[] A_6, h2
A_7)
at EO.Pdf.Internal.dc.a(HtmlToPdfOptions A_0, String A_1, Boolean A_2)
at EO.Pdf.Internal.dc.b(HtmlToPdfOptions A_0, String A_1, Boolean A_2)
at EO.Pdf.Internal.dc.a(hi A_0)
at EO.Pdf.Internal.lr.c.a(hi A_0)
at EO.Pdf.Internal.lr.c.a(Byte[] A_0)
We don't know what exactly can cause this type of error, because it happens just sometimes (during last 14 days just twice). We use your component for scheduling report, therefore this component is hosted in our process which runs as windows service and for scheduling using ncrontab (http://code.google.com/p/ncron/downloads/detail?name=ncron-2.1.zip). I don't know if this can relate with, that it is hosted in process where runs other tasks in threads, but according what I find here:
http://www.essentialobjects.com/forum/postsm31506_AccessViolationError-when-generating-PDFs-with-multiple-threads.aspx where someone had similar issue, but I don't see that it was finally resolved, it will not be related to other threads. I have question whether you solved similar issue and was able to resolve into new released version or not or if you have idea what can cause this type of issue. Do you use some unsafe access to memory in your component which could lead to this type of issue?
We upgraded from EO.Pdf version 3.0.104.2 there we didn't have this type of issue, but because this component has lot of others flaws we can't downgrade.
Thanks for response