MantisCore Posted July 12, 2023 Share Posted July 12, 2023 Publisher (version 2.1.1) is consistently crashing whenever I try to apply a master to another master page in my document. It works fine in a brand new document and used to work in this one as well so I assume it is something that happened over time. According to the Event Viewer the crash is caused by an AccessViolationException (see below) so I assume there is some memory handling issue at fault here. Document displaying the issue is attached below. Application: Publisher.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at <Module>.ApplyMasterPageCommand.CanPlaceMaster(Kernel.Counted<DocumentController const >*, Int32, Int32) at Serif.Interop.Persona.Data.PagesPageDataSource.CouldApplyMaster(Int32, Int32) at Serif.Interop.Persona.Data.ApplyMasterToMasterDataSource.UpdateEnabled() at Serif.Affinity.UI.Studio.Pages.PagesPageViewModel.<PrepareCommands>b__102_16(System.Object) at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(System.Windows.Input.ICommandSource, Boolean) at System.Windows.Controls.MenuItem.InvokeClickAfterRender(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 Publisher.Application.Main(System.String[]) test.afpub Quote Link to comment Share on other sites More sharing options...
Dan C Posted July 12, 2023 Share Posted July 12, 2023 Hi @MantisCore, Thanks for your report and file provided! I can confirm that I've been able to replicate your issue here, it appears to be caused due to the 'Internal Page' and 'Internal Page Text' Master Pages - I can see they reference other Master Pages, however that exact link has become broken, causing the crash when applying any new master pages. Do you recall the most recent steps taken in this file, specifically regarding these master pages? In the meantime I will be sure to log this with our development team to be investigated further and try to handle this better in the future Quote Link to comment Share on other sites More sharing options...
MantisCore Posted July 12, 2023 Author Share Posted July 12, 2023 Thanks for the reply @Dan C These particular pages were synced from a different file belonging to the same book (using the Books pane). I tested the other file and that one seems to work fine. If I recall correctly multiple syncs caused duplicates of the master pages pages to appear in this file so I removed the extra ones manually. Could that be the cause of the problem? Quote Link to comment Share on other sites More sharing options...
Dan C Posted July 12, 2023 Share Posted July 12, 2023 No problem at all, thanks for letting me know - this certainly could have caused the issue inadvertently, as it sounds as though when manually deleting one of the duplicate masters the link was lost between the original master, causing the crash when applying any further masters to another. I'll be sure to include this information within the development report to help them narrow down the exact cause Quote Link to comment Share on other sites More sharing options...
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.