I am using the wkHTMLtoXSharp wrapper to call the wkHTMLtoPDF library on Windows 2008 R2. It’s all working great with one exception. I’m calling the wrapper from a C# windows service. On the first run the conversion works flawlessly. On subsequent runs I get memory corruption or AccessViolationException. The only way to fix it is to kill the process that the DLL is running in. That seems to reset the underlying issue. Any clue how to troubleshoot this?
I am using the wkHTMLtoXSharp wrapper to call the wkHTMLtoPDF library on Windows 2008
Share
Sure Zubrowka. I tried every trick I’m familiar with to overcome the memory corruption without much luck.
Given that the first run was working flawlessly, I decided to wrap the PDF call in an executable and called the CommandLine executable via ProcessStartInfo. This is working just fine for me. I prefered not to cause as much context switching, however, it’s the lesser of both evils.