Crashing with Out of Memory Error?

Tue, Feb 5, 2013

Update on this bug:

I have finally experienced this and have a crash dump for it. It does not look like a driver/video card problem, but a WPF bug. I’m going to recode the alert window to remove some smoothing optimization which appear to be the culprit. The added code made the DX Overlays “clearer” but appears to have caused a framework bug to be hit.

The bug can happen at any time regardless of whether EQ2 is running and regardless of user action. It crashed on me while simply playing EQ2, and while replaying raids without EQ2 running (trying to trip the bug in fact!).

Release 1.1.30 and forward will have this extra code removed and the crashes will stop.

NOTE: this applies if you are experiencing crashes with the dialog saying something like:

RaidHubClient.exe Error: 0 : Exception Caught: System.OutOfMemoryException: Insufficient memory to continue the execution of the program.
at System.Windows.Media.Composition.DUCE.Channel.SyncFlush()
at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, Nullable`1 channelSet)
at System.Windows.Interop.HwndTarget.UpdateWindowPos(IntPtr lParam)
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)