Hi,

I am using Patagames.PDF.WPF version 3.5.5 to display pdfs in my application, and I experienced a strange error when I tried maximizing my application to an unusually wide screen resolution. It happened while using the software through Remote Desktop which seemed to have a dual screen resolution registered as a single screen for some reason. The app crashed with the following call stack:
Patagames.Pdf.Net.Exceptions.PdfiumException: Unexpected error code.
at Patagames.Pdf.Pdfium.ProcessLastError()
at Patagames.Pdf.Net.Controls.Wpf.PRCollection.InitCanvas(Int32Size size)
at Patagames.Pdf.Net.Controls.Wpf.PdfViewer.OnRender(DrawingContext drawingContext)
at System.Windows.UIElement.Arrange(Rect finalRect)
at System.Windows.ContextLayoutManager.UpdateLayout()
at System.Windows.ContextLayoutManager.UpdateLayoutCallback(Object arg)
at System.Windows.Media.MediaContext.InvokeOnRenderCallback.DoWork()
at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
at System.Windows.Media.MediaContext.RenderMessageHandlerCore(Object resizedCompositionTarget)
at System.Windows.Media.MediaContext.RenderMessageHandler(Object resizedCompositionTarget)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)

Then when I tried to restart my application (which tried to render it in its maximized state), I got repeated out of memory exceptions, so I had to completely restart the computer in order to run the app again. I tried recreating this error with no luck, but I do see my application's memory spike significantly (>400mb additional) if I drag my app to fill both screens of a dual screen setup, and I can cause an out of memory exception if I do a lot of rapid resizing of the pdf viewer. This makes me think that the original error was caused by some sort of out of memory exception which was never cleaned up after the crash, which would explain why the app could no longer start up. Is there something I can do to prevent this? Perhaps just put a maximum size on the control? Or have you guys addressed this memory consumption issue in a later release?