Hi we're experiencing a OutOfMemoryException when a user tries to drag a window to another location. As soon as the drag starts the the docking locators show and the whole window freezes.
It seems to happen when using a terminal services session and remoting onto a box, or using HP RGS and logging in. When using an RDP session and the resolution is quite high e.g. 4096x1050 it's easier to recreate.
We've seen a couple of different possibilities for the exception via google, a possible one from microsoft involving WriteableBitmaps. Is this used in the docking librbary? We have the DockManager using deferred FloatingWindowDragMode.
Thanks, Mark.
Infragistics version:
12.2.20122.2022
Stack Trace:
System.OutOfMemoryException: Insufficient memory to continue the execution of the program. at System.Windows.Media.Composition.DUCE.Channel.SyncFlush() at System.Windows.Media.MediaContext.CompleteRender() at System.Windows.Interop.HwndTarget.OnResize() at System.Windows.Interop.HwndTarget.HandleMessage(WindowMessage msg, IntPtr wparam, IntPtr lparam) at System.Windows.Interop.HwndSource.HwndTargetFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
Hello Mark,
Excuse me for the late reply, I have been looking into your issue and trying to replicate an environment with such a resolution. I managed to get an XP virtual machine with such a resolution, however with your xaml snippet I saw no such issue whatsoever. I was wondering if you could please describe your environment in as much details as possible, so I can try and replicate it.
Looking forward to hearing from you.
Hi Petar, thanks for your response. We've managed to resolve the issue by updating the graphics drivers on the effected boxes. It seems to be very much tied to using older nvidia graphics drivers.
I am really glad to hear that you have this worked out.