Hi,

We are currently in the process of upgrading from version 4.0 to the latest version of EO.Pdf. However I stumbled upon multiple problems. But the most blocking issue is pages getting cut off. I can improve the results by increasing MinLoadWaitTime. I tried 0, 1, 100, 1000, 2500, 5000 and 10,000. Only with 10k I can consistently get good results. Every increase does usually improve it somewhat but only with 10k we get the expected results.

We fetch our pages with a WebClient and then feed the html to EO.Pdf. We use the Manual TriggerMode and eopdf.convert() when the page is ready. All XHR resources and transformation code should have been executed at the moment we call convert. It might still be working on fetching some images but the outline of the page should long be finished by the time we call convert(). I can confirm that it will still print the outline of the page when I seriously delay the data call that will fill in some text and numbers. But it will somehow cut off the outline with a low WaitTime. I also have a page with regular html tables with text only being printed half (divided horizontally).

In the previous version we had the TriggerMode set to Manual and the MinLoadWaitTime to 1. This way all our pages would report just fine, even when we would still fetch resources after the convert call. For clarity: we fixed convert being called too early in the problem described in the second paragraph. So things should be loaded by the time we call convert.

The 10k as MinLoadWaitTime will make our reporting take more than twice as long which is not really acceptable. Do you know what could be wrong on our side? Have you heard of similar cases?

Thanks in advance!

Kind regards,
Marvin