App fails on restart problem ?
-
We have a WPF app with about 400 users. One user, who has a high end machine ( 2 gig of RAM, good video card, etc ), reports that if he starts the app on boot, closes it and restarts it, it blows up. That is to say, at any point if he runs it a second time, it fails, even if he does it all right away. Here is the stack trace: Not enough quota is available to process this command at MS.Win32.UnsafeNativeMethods.PostMessage(HandleRef hwnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, List`1 channelList) 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) We have our own logging in the app, I know for sure that the constructor for te MainWindow is completed, or in this code: bool current = OvsUtility.GetInterfaceAnimalPanel().DualOverlaysOn; singleOverlay.IsChecked = !current; dualOverlay.IsChecked = current; singleOverLay and dualOverlay are menu items, GetInterfaceAnimalPanel just returns an inner control from a user control. We have no logging after this code, but we have logging the moment the Load event fires on the Main Window, and this code is not running, so the exception occurs in the above code, OR between the constructor and the Load event. The only code that runs between these two, is a couple of window size changed events. I assume it's something to do with his machine, as no-one else has the issue, but it's not low specced, so that's not it. Where do I look next ?
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven
-
We have a WPF app with about 400 users. One user, who has a high end machine ( 2 gig of RAM, good video card, etc ), reports that if he starts the app on boot, closes it and restarts it, it blows up. That is to say, at any point if he runs it a second time, it fails, even if he does it all right away. Here is the stack trace: Not enough quota is available to process this command at MS.Win32.UnsafeNativeMethods.PostMessage(HandleRef hwnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, List`1 channelList) 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) We have our own logging in the app, I know for sure that the constructor for te MainWindow is completed, or in this code: bool current = OvsUtility.GetInterfaceAnimalPanel().DualOverlaysOn; singleOverlay.IsChecked = !current; dualOverlay.IsChecked = current; singleOverLay and dualOverlay are menu items, GetInterfaceAnimalPanel just returns an inner control from a user control. We have no logging after this code, but we have logging the moment the Load event fires on the Main Window, and this code is not running, so the exception occurs in the above code, OR between the constructor and the Load event. The only code that runs between these two, is a couple of window size changed events. I assume it's something to do with his machine, as no-one else has the issue, but it's not low specced, so that's not it. Where do I look next ?
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven
Christian, Did you ever figure this out?
Cheers, Karl» CodeProject 2008 MVP » Microsoft MVP - Client App Dev My Blog | Mole's Home Page | MVP ProfileJust a grain of sand on the worlds beaches.
-
We have a WPF app with about 400 users. One user, who has a high end machine ( 2 gig of RAM, good video card, etc ), reports that if he starts the app on boot, closes it and restarts it, it blows up. That is to say, at any point if he runs it a second time, it fails, even if he does it all right away. Here is the stack trace: Not enough quota is available to process this command at MS.Win32.UnsafeNativeMethods.PostMessage(HandleRef hwnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, List`1 channelList) 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) We have our own logging in the app, I know for sure that the constructor for te MainWindow is completed, or in this code: bool current = OvsUtility.GetInterfaceAnimalPanel().DualOverlaysOn; singleOverlay.IsChecked = !current; dualOverlay.IsChecked = current; singleOverLay and dualOverlay are menu items, GetInterfaceAnimalPanel just returns an inner control from a user control. We have no logging after this code, but we have logging the moment the Load event fires on the Main Window, and this code is not running, so the exception occurs in the above code, OR between the constructor and the Load event. The only code that runs between these two, is a couple of window size changed events. I assume it's something to do with his machine, as no-one else has the issue, but it's not low specced, so that's not it. Where do I look next ?
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven
-
We have a WPF app with about 400 users. One user, who has a high end machine ( 2 gig of RAM, good video card, etc ), reports that if he starts the app on boot, closes it and restarts it, it blows up. That is to say, at any point if he runs it a second time, it fails, even if he does it all right away. Here is the stack trace: Not enough quota is available to process this command at MS.Win32.UnsafeNativeMethods.PostMessage(HandleRef hwnd, Int32 msg, IntPtr wparam, IntPtr lparam) at System.Windows.Interop.HwndTarget.UpdateWindowSettings(Boolean enableRenderTarget, List`1 channelList) 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) We have our own logging in the app, I know for sure that the constructor for te MainWindow is completed, or in this code: bool current = OvsUtility.GetInterfaceAnimalPanel().DualOverlaysOn; singleOverlay.IsChecked = !current; dualOverlay.IsChecked = current; singleOverLay and dualOverlay are menu items, GetInterfaceAnimalPanel just returns an inner control from a user control. We have no logging after this code, but we have logging the moment the Load event fires on the Main Window, and this code is not running, so the exception occurs in the above code, OR between the constructor and the Load event. The only code that runs between these two, is a couple of window size changed events. I assume it's something to do with his machine, as no-one else has the issue, but it's not low specced, so that's not it. Where do I look next ?
Christian Graus Please read this if you don't understand the answer I've given you "also I don't think "TranslateOneToTwoBillion OneHundredAndFortySevenMillion FourHundredAndEightyThreeThousand SixHundredAndFortySeven