crash on start up

[illuminaughty]

when ever i start up the application it crashes, the window pops up for me to enter my credentials and halfway through typing it just disappears. this is the only thing that shows up in the event viewer.

Application: Designer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at <Module>.Renderer.FontMetrics.Make(Kernel.Counted<Renderer::FontMetrics const >*, Kernel.Font*)
   at Serif.Interop.Persona.UserInterface.FontCellControlHelper.CanRender(Kernel.Font*)
   at Serif.Interop.Persona.UserInterface.FontCellControlHelper.CreatePreviewBitmap(System.ComponentModel.BackgroundWorker)
   at Serif.Interop.Persona.UserInterface.FontCellControlHelper.EnumFontsW(System.Object, System.ComponentModel.DoWorkEventArgs)
   at System.ComponentModel.BackgroundWorker.OnDoWork(System.ComponentModel.DoWorkEventArgs)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(System.Object)

Exception Info: System.Reflection.TargetInvocationException
   at System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
   at Serif.Interop.Persona.UserInterface.FontCellControlHelper.OnRunWorkerCompleted(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs)
   at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(System.ComponentModel.RunWorkerCompletedEventArgs)
   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.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()

and this 

Application: Photo.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at <Module>.Renderer.FontMetrics.Make(Kernel.Counted<Renderer::FontMetrics const >*, Kernel.Font*)
   at Serif.Interop.Persona.UserInterface.FontCellControlHelper.CanRender(Kernel.Font*)
   at Serif.Interop.Persona.UserInterface.FontCellControlHelper.CreatePreviewBitmap(System.ComponentModel.BackgroundWorker)
   at Serif.Interop.Persona.UserInterface.FontCellControlHelper.EnumFontsW(System.Object, System.ComponentModel.DoWorkEventArgs)
   at System.ComponentModel.BackgroundWorker.OnDoWork(System.ComponentModel.DoWorkEventArgs)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(System.Object)

Exception Info: System.Reflection.TargetInvocationException
   at System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
   at Serif.Interop.Persona.UserInterface.FontCellControlHelper.OnRunWorkerCompleted(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs)
   at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(System.ComponentModel.RunWorkerCompletedEventArgs)
   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.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
 

[Callum]

Hi illuminaughty,

If you haven't already please could you try reinstalling the app? Please could you also confirm if you are using the MSIX or MSIEXE version of the apps?

Thanks
C

[illuminaughty]

@Callum

ive tried reinstalling the app several times to no avail. I don't know i see if there is a different version i can download. I'm a mac guy I'm new to windows. 

Edited May 5 by illuminaughty

[illuminaughty]

I have the msix version. i downloaded the exe version and I'm gonna try downloading it from the Microsoft store to see if that helps

[illuminaughty]

@Callum well it looks like the msix and the one downloaded from the store both crash on start up now trying the exe 

[illuminaughty]

@Callum looks like all of them crash at the same point. Here is what info i can find on what caused it. BTW all apps crash. 

 

Application: Designer.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
   at <Module>.Renderer.FontMetrics.Make(Kernel.Counted<Renderer::FontMetrics const >*, Kernel.Font*)
   at Serif.Interop.Persona.UserInterface.FontCellControlHelper.CanRender(Kernel.Font*)
   at Serif.Interop.Persona.UserInterface.FontCellControlHelper.CreatePreviewBitmap(System.ComponentModel.BackgroundWorker)
   at Serif.Interop.Persona.UserInterface.FontCellControlHelper.EnumFontsW(System.Object, System.ComponentModel.DoWorkEventArgs)
   at System.ComponentModel.BackgroundWorker.OnDoWork(System.ComponentModel.DoWorkEventArgs)
   at System.ComponentModel.BackgroundWorker.WorkerThreadStart(System.Object)

Exception Info: System.Reflection.TargetInvocationException
   at System.ComponentModel.AsyncCompletedEventArgs.RaiseExceptionIfNecessary()
   at Serif.Interop.Persona.UserInterface.FontCellControlHelper.OnRunWorkerCompleted(System.Object, System.ComponentModel.RunWorkerCompletedEventArgs)
   at System.ComponentModel.BackgroundWorker.OnRunWorkerCompleted(System.ComponentModel.RunWorkerCompletedEventArgs)
   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.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
 

Here is what Chat GPT had to say about the error

The crash log you've provided for the application Designer.exe points to a fatal error caused by an System.AccessViolationException. This exception usually occurs when an application tries to read or write to a memory location that it does not have access to, which is often a sign of a serious issue within the code.

Here's a breakdown of what the log suggests and some potential fixes:

Causes of System.AccessViolationException:
Unsafe Code: The error occurs inside the Renderer.FontMetrics.Make method, which likely involves operations on unmanaged resources or direct memory manipulation. If unsafe code is being used, any pointer arithmetic or memory manipulation errors could lead to access violations.
Interop Operations: The stack trace includes several references to interop services (Serif.Interop.Persona). If the application is interfacing with unmanaged code or external libraries, incorrect marshaling of data types or lifecycle management of unmanaged resources could be the cause.
Concurrent Modifications: Since the error involves a BackgroundWorker, there might be concurrent access issues, especially if shared resources are being modified without proper synchronization.

Steps to Troubleshoot and Fix:
Review Unsafe Code: If the application uses unsafe code blocks or interacts with unmanaged libraries, review these sections carefully. Check for proper memory allocation, deallocation, and access patterns.
Check Interop Definitions: Ensure that all interop calls have the correct data type mappings and that any unmanaged memory is managed correctly. Pay special attention to the lifecycle of objects that are shared between managed and unmanaged code.
Manage Concurrency: Ensure that objects shared between threads are properly synchronized. If the BackgroundWorker is manipulating shared resources, consider using locks, mutexes, or other synchronization primitives to prevent concurrent modifications.
Testing and Debugging:
Debugging: Run the application under a debugger and set breakpoints around the failing methods to observe the state of the application just before the crash.
Logging: Increase logging around the crash site to capture more detailed information about the application's state and sequence of operations leading up to the crash.
Stress and Unit Testing: Specifically test the font loading and rendering functionalities under various scenarios to reproduce and isolate the issue.
Memory Tools: Use memory profiling and debugging tools to detect issues like buffer overruns, memory leaks, or improper access patterns, which might be causing the access violation.
Update and Patch: Ensure that all libraries and frameworks used by the application are up-to-date. Sometimes, bugs in external libraries can cause these types of exceptions.
By following these steps, you should be able to pinpoint the exact cause of the System.AccessViolationException and implement a fix. If you're not familiar with debugging or working with unmanaged code, consider consulting with a developer who has experience in these areas.