|
|
Rank: Member
Groups: Member
Joined: 6/16/2014
Posts: 22
|
EO.Pdf.Internal.agl+NativeException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt. ---> System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.DoEvents()
at EO.Pdf.Internal.ae2.a(WaitHandle A_0, Int32 A_1, fl A_2)
--- End of inner exception stack trace ---
at EO.Pdf.Internal.am5.i()
at EO.Pdf.Internal.md.a(Int32 A_0, Int32 A_1, String A_2, Int32 A_3)
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
This can happen. EO.Pdf is based on WebKit and just like other browser engines, occasionally it can crash. However EO.Pdf runs the WebKit browser engine inside a separate process so that in case it did crash, it will not crash your process directly. Instead you will be able to detect it by catching an exception (such as NativeException that you have it here) and handle it gracefully (for example, try the conversion again).
There are other type of exceptions that can occur during the conversion as well. For example, you may run into OutOfMemoryException if the file is too big. Or you may run into AccessException if it tries to save a file but the file is currently open elsewhere. All of them will crash your program if you do not handle them. On this regard this exception is no different than the NativeExcpetion.
In your case, the "Attempted to read or write protected memory" is mostly caused by an out of memory situation --- the native code tries to allocate some memory but failed. So you may want to handle this exception the same way as an OutOfMemoryException. Of course, if the exception always occurs, then it's a different story. If that's the case please let us know.
Thanks!
|
|
Rank: Member
Groups: Member
Joined: 6/16/2014
Posts: 22
|
Yes..it occurs in every attempt of the same page..this page has an SVG chart using HighCharts js framework and a grid with 1000 rows with Kendo UI. We tried commenting the chart and crash stopped, but the rendering took infinite time and rundll32.exe was 99% CPU,we had to kill the process after some 15 minutes..We don't have problems with similar pages with same Grid with 1000+ rows.
|
|
Rank: Administration
Groups: Administration
Joined: 5/27/2007
Posts: 24,229
|
Hi,
Do you have the page online so that we can try to debug it from here?
Thanks!
|
|