Hi,
I'm glad to hear that you're working on the problem and it's fine if it takes some time to solve it. Related to this problem is the issue that memory seems to be corrupted after an attempt was made to convert the erroneous pdf. So attempts made to convert valid pdf's, which have been successfully been converted before, will throw the following exception:
[AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory has been corrupted.]
System.Diagnostics.StackTrace.GetStackFramesInternal(StackFrameHelper sfh, Int32 iSkip, Exception e) +0
System.Diagnostics.StackTrace.CaptureStackTrace(Int32 iSkip, Boolean fNeedFileInfo, Thread targetThread, Exception e) +54
System.Diagnostics.StackTrace..ctor(Exception e, Boolean fNeedFileInfo) +38
System.Web.UnhandledErrorFormatter.get_ColoredSquare2Content() +586
System.Web.UnhandledErrorFormatter.PrepareFormatter() +45
System.Web.ErrorFormatter.GetHtmlErrorMessage(Boolean dontShowSensitiveInfo) +56
System.Web.HttpResponse.WriteErrorMessage(Exception e, Boolean dontShowSensitiveErrors) +590
System.Web.HttpResponse.ReportRuntimeError(Exception e, Boolean canThrow, Boolean localExecute) +225
System.Web.HttpRuntime.FinishRequest(HttpWorkerRequest wr, HttpContext context, Exception e) +383
And this is very annoying and is causing more problems for us than the failed conversion problem itself. So we'd like to see this problem solved first if possible.
I have to add that we're running Aspose.Pdf.Kit in an Asp.Net environment.
Gr.
Lokhan Wong
DTZ Zadelhoff
P.S.: To reproduce the problem, take the erroneous pdf and try to convert it. After it failed, try to convert a valid pdf. It may take several attempts and we only tried this in an Asp.Net environment.
