Hi,

We recently upgraded our EO.pdf version from 15 to version 17.1.76 and we have noticed that we are getting
an amount of errors see stacktrace below:

Message: This WebView either has already been destroyed or is being destroyed.

EO.Base.Runtime.a(Object A_0, Exception A_1, Boolean A_2):285
EO.WebBrowser.WebView.s():169
EO.WebBrowser.WebView.LoadHtml(String html, String baseUrl):8
EO.Internal.pa.a(adj A_0, String A_1, String A_2, String A_3, Int32 A_4, Int32 A_5, String A_6, Boolean A_7):430
EO.Pdf.HtmlToPdfSession.a(adj A_0, String A_1, String A_2, Int32 A_3, Int32 A_4, String A_5, Boolean A_6):114
EO.Pdf.HtmlToPdf.ConvertHtml(String html, PdfDocument doc, HtmlToPdfOptions options):54

We dont always get this error, but when we get it the error stops occuring after we restart our website in IIS.
When we searched for the error message we came upon this forum post: https://www.essentialobjects.com/forum/postst10100_Async-QueueSciptCall-causes-This-WebView-either-has-already-been-destroyed-or-is-being-destroy.aspx.
However we dont understand the solution to the problem.

We hope you guys could help us with this issue.

Thank you very much.

Hey,

Thank you for your response, we have no idea how to reproduce this problem because its rather random.
But we may have discovered something that it could have started with this exception below:

Message: Conversion failed. Browser engine failed to render page. Failed on command 2

EO.Pdf.HtmlToPdfException.b(Exception A_0):26
EO.Internal.a3e.a(af4 A_0):2997
EO.Pdf.HtmlToPdfSession.RenderAsPDF(PdfDocument doc):199
EO.Pdf.HtmlToPdf.ConvertHtml(String html, PdfDocument doc, HtmlToPdfOptions options):54

InnerException:

Message: Browser engine failed to render page. Failed on command 2

EO.Internal.pa.a(String A_0):35
EO.Internal.pa.a(b A_0, a7z A_1, WriteArgDelegate A_2):559
EO.Internal.pa.a(Boolean A_0):29
EO.Internal.pa.a(HtmlToPdfOptions A_0, Single A_1, Single A_2, amc A_3, List`1 A_4, af4 A_5):0
EO.Internal.a3e.a(af4 A_0, Single& A_1):108
EO.Internal.a3e.a(af4 A_0):394

When this exception occured, the other exception (see previous post) comes next, maybe this brings us closer to a solution.

Thank you very much.

Hi,

We have looked into the sample project you sent to us. The crash on large image is not avoidable. However the fact that you must restart your IIS after the crash is an issue and needs to be resolved, unfortunately we can not reproduce this issue.

We have performed the following test:

1. Create a simple Web application and run the code you provided as is. The conversion fails with an exception. Since there are no user code to catch this exception, the exception is caught and handled by ASP.NET, which display the standard ASP.NET error page and stack trace;

2. Based on the above code, uses a try catch block around the conversion. The exception is thrown and eaten by the catch block. The application proceed without displaying an error message;

In both cases, we then try to access another page that performs a "normal" conversion and it works fine. So in our case the application did not need to be restarted.

You may see a "Runtime Exception" dialog during your test. You can ignore or close that dialog. It should not alter the result. That dialog is automatically silenced if Environment.UserInteractive is false (which should be the case in your production environment), or you can manually silence it by handling EO.Base.Runtime.Exception event.

Please let us know if you see the same result if you try the above test.

Thanks!