System.Runtime.InteropServices.COMException being thrown on WPF application on Win7 x64

Question

Guys, what is causing this exception in my .NET 3.5 WPF app?  Never seen it before till I deployed application on Win 7 x64.  Applicationw as compiled using Any CPU.  We tried x86 but ran into different kind of problems, including application running out of memory. Is this fixable?

ErrorCode : -2003303418
Data : System.Collections.ListDictionaryInternal
TargetSite : Void SyncFlush()
Stack Trace :    at System.Windows.Media.Composition.DUCE.Channel.SyncFlush()
   at System.Windows.Media.Composition.DUCE.CompositionTarget.UpdateWindowSettings(ResourceHandle hCompositionTarget, RECT windowRect, Color colorKey, Single constantAlpha, MILWindowLayerType windowLayerType, MILTransparencyFlags transparencyMode, Boolean isChild, Boolean isRTL, Boolean renderingEnabled, Int32 disableCookie, Channel channel)
   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(Int32 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, Boolean isSingleParameter)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)

Answer 1

Try disabling 3D acceleration on your graphics card, I found the following article that said it had solved the issue - http://blog.allanglen.com/2010/01/running-wpf-apps-in-virtualbox

Hope it helps,

Aj

PS: If you're not able to run it on a x86 machine and are getting different errors, you may have other underlying issues to address...post your other stack trace...it may shed some light on the subject if the above doesn't work for you.

---

If at first you don't succeed, skydiving is definitely not for you!

Answer 2

Thanks for the response.  Application runs fine on x86, however, if compiled as x86 and deployed on Win 7 x64, we run into different kinds of problems, including application running out of memory, something that does not happen when running on x86.

Thanks for the link.  Will try it out.

Answer 3

Wouldn't be the first bizarre thing I've seen like that...tough to say without the project and more familiarity with it, but often times hardware and other software on the machine will cause issues with certain WMI features and or the way in which WPF renders graphics...it's a grab-bag of fun issues...you'll never know what you pick out next...lol.

Hope it helps,

Aj

---

If at first you don't succeed, skydiving is definitely not for you!

Answer 4

There has been a similiar issue in  http://connect.microsoft.com/VisualStudio/feedback/details/500410/wpf-crashes-with-error-hresult-0x88980406.

Also a bug has been created for it, however not fixed yet.

---

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Regards,
Jacky Wu
Microsoft Online Community Support