maxenko Posted January 4, 2023 Posted January 4, 2023 I am experiencing a crash immediately after trying to start the application. Splash screen goes away and process hangs. This is a fresh install of Affinity Designer 2 Event viewer is showing this exception from Designer.exe Application: Designer.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.ComponentModel.Win32Exception at MS.Win32.UnsafeNativeMethods.GetWindowText(System.Runtime.InteropServices.HandleRef, System.Text.StringBuilder, Int32) at System.Windows.Automation.Peers.WindowAutomationPeer.GetNameCore() at System.Windows.Automation.Peers.AutomationPeer.UpdateSubtree() at System.Windows.ContextLayoutManager.fireAutomationEvents() at System.Windows.ContextLayoutManager.UpdateLayout() at System.Windows.ContextLayoutManager.UpdateLayoutCallback(System.Object) at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks() at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object) at System.Windows.Media.MediaContext.RenderMessageHandler(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at Designer.Application.Main(System.String[]) Possibly related to this?: https://stackoverflow.com/questions/70799521/random-crash-in-wpf-application-invalid-index-at-ms-win32-unsafenativemethods Please advise. Quote
SrPx Posted January 4, 2023 Posted January 4, 2023 A lot of problems seem to go away by deactivating hardware acceleration - Open CL. When you can't disable that in preferences, as it happens just in the splash, you can try to launch the app with a parameter that disables it : Quote AD, AP and APub V2.5.x. Windows 10 and Windows 11.
maxenko Posted January 4, 2023 Author Posted January 4, 2023 20 hours ago, SrPx said: A lot of problems seem to go away by deactivating hardware acceleration - Open CL. When you can't disable that in preferences, as it happens just in the splash, you can try to launch the app with a parameter that disables it : Unfortunately, it doesn't help, same behavior. The exception is complaining about something to do with a window handle, so unlikely related to hardware acceleration. Thank you for your suggestion! SrPx 1 Quote
SrPx Posted January 4, 2023 Posted January 4, 2023 Do you have Windows updated to the last update ? .NET fine, and everything ? As it could be that... Also be sure to have the latest version for your graphic driver (uninstall it first, though!). Quote AD, AP and APub V2.5.x. Windows 10 and Windows 11.
maxenko Posted January 5, 2023 Author Posted January 5, 2023 18 hours ago, SrPx said: Do you have Windows updated to the last update ? .NET fine, and everything ? As it could be that... Also be sure to have the latest version for your graphic driver (uninstall it first, though!). .NET is latest, windows version is 19044.2364 (also latest atm). Graphic driver is also latest (Quadro A6000). Quote
maxenko Posted January 5, 2023 Author Posted January 5, 2023 It really does look like this:https://github.com/dotnet/wpf/pull/7345 Quote
Staff Callum Posted January 30, 2023 Staff Posted January 30, 2023 Hi Maxenko, Does this still occur with our latest 2.0.4 version released last Friday? Alternatively .EXE builds of the apps are now available from their downloads page on our website it may be worth trying these to see if they solve this issue for you. https://forum.affinity.serif.com/index.php?/topic/180014-affinity-v2-windows-installers-are-available-as-unsandboxed-msiexe-as-well-as-sandboxed-msix/ Thanks C maxenko 1 Quote Please tag me using @ in your reply so I can be sure to respond ASAP.
maxenko Posted February 14, 2023 Author Posted February 14, 2023 On 1/30/2023 at 4:57 AM, Callum said: Hi Maxenko, Does this still occur with our latest 2.0.4 version released last Friday? 2.0.4 works, thank you! Got past the launch screen and now running. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.