Affinity Publisher crashes after opening APUB file

[FAEGames]

I now have an issue where any v2 document I open in Affinity Publisher 2.0.4 will open the file and shortly after crash. I can see everything loading, but I can't work on anything anymore.

Version: 2.0.4
OS: Windows
Install type: MSIX

Where can I find the crash logs for v2? I want to share them, but I'm unable to find them in the previous location.

[FAEGames]

I actually found a lot of interesting information in the Event Viewer:

Faulting application name: Publisher.exe, version: 2.0.4.1701, time stamp: 0x63ceb04f
Faulting module name: ntdll.dll, version: 10.0.19041.2788, time stamp: 0x2f715b17
Exception code: 0xc0000374
Fault offset: 0x00000000000ff449
Faulting process ID: 0x349c
Faulting application start time: 0x01d971847b36017b
Faulting application path: C:\Program Files\WindowsApps\SerifEuropeLtd.AffinityPublisher2_2.0.4.1701_x64__3cqzy0nppv2rt\App\Publisher.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 50cbe174-13bb-4cef-bbd3-faaf0ca716a9
Faulting package full name: SerifEuropeLtd.AffinityPublisher2_2.0.4.1701_x64__3cqzy0nppv2rt
Faulting package-relative application ID: SerifEuropeLtd.AffinityPublisher2

Affinity-errors.evtx

[FAEGames]

Also tried with the beta. Same result:

Faulting application name: Publisher.exe, version: 2.1.0.1742, time stamp: 0x642d2b58
Faulting module name: ntdll.dll, version: 10.0.19041.2788, time stamp: 0x2f715b17
Exception code: 0xc0000374
Fault offset: 0x00000000000ff449
Faulting process ID: 0x1370
Faulting application start time: 0x01d97187749da2ba
Faulting application path: C:\Program Files\Affinity\Publisher 2 Beta\Publisher.exe
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report ID: 484d5c8d-ec62-4514-b586-893f1c66bdf1
Faulting package full name: 
Faulting package-relative application ID: 

[MikeTO]

Hi, are you able to create new documents and save them successfully? i.e., is the problem just with opening your existing documents?

If nothing else works, try starting Publisher while holding down Ctrl and then reset your user data.

Good luck

[stokerg]

Hi @FAEGames,

13 hours ago, FAEGames said:

Where can I find the crash logs for v2?

Please see here:https://forum.affinity.serif.com/index.php?/topic/168448-where-do-i-find-crash-reports-for-affinity-v2-apps/ and attach the latest crash report (just the latest one will do).  

As @MikeTOhas also said, does this happen only for existing documents? If it does, can you attach one here?

 

[FAEGames]

@stokergUnfortunately there are no recorded crash reports in that directory. Only the Windows events. I can't share the document with you publicly because of the copyrighted material within.

It definitely has to do with the JPG images I've added, because removing them has restored my document in working order, though I have to find another way to include the images. I do have a crashing copy still though.

[FAEGames]

Yup, this definitely had to do with applying additional layers and effects to JPGs added to a picture frame. I've salvaged the document and redid all the pictures as APUBs and flattened them before placing them once again in my document. Now it's opening again without issue.

It was either:

- The background erase brush that spiralled out of control

- The layer with a triangle shape, gaussian blur, and perspective effect to create a shadow

I still have a crashing copy if I could share it directly with you @stokerg

[stokerg]

Hi @FAEGames,

If you could upload the document to our Dropbox here: https://www.dropbox.com/request/IsXVBVrHX4rRL42igcfN and make sure to include some of the images if they are only linked and not embedded and I'll be able to see if I can replicate the crash.

 

[FAEGames]

4 hours ago, stokerg said:

Hi @FAEGames,

If you could upload the document to our Dropbox here: https://www.dropbox.com/request/IsXVBVrHX4rRL42igcfN and make sure to include some of the images if they are only linked and not embedded and I'll be able to see if I can replicate the crash.

 

I've uploaded the file with some of the images embedded. In my attempts to come to a working copy I believe I've managed to create a minimal version that crashes.

[FAEGames]

@stokergWere you able to discern some issue? I haven't encountered this anymore with other documents, but I avoided having embedded images from now on.

[FAEGames]

Had this again with a v1 document that I converted today. I quickly deleted the crashing image and saved the document before it crashed again and then re-added the image as a linked resource again. It seems that certain embedded images cause a stack or memory overflow in v2.

[FAEGames]

@stokerg this issue is also occurring on 2.1.1. I notice it's fixed when switching graphics card in the Performance settings. I have an Intel 630 and a Geforce GTX 1650. Today it worked when I switched to Intel and the time before I had to switch to the Geforce.