Affinity Publisher 2 crashes instantly with no crash log when Ctrl+C or Duplicating a specific page (reproduced on two machines)

[Mycoscopic]

1. I'm using Publisher 2. I also have Designer 2 installed.
2. I'm using the latest version, 2.6.0.
3. I can reproduce using the same file on two different Windows machines.
4. I have uploaded the problem document.
5. Details:
   1. Operating system: Two machines. Windows 10 Pro 10.0.19045 and Windows 10 Home 10.0.19045.
   2. Hardware acceleration is ON, but it still happens after turning it OFF.
   3. What happened: When I Duplicate Page 4 (right click in page menu) or select everything on Page 4 and copy it (drag select and Ctrl+C) in the attached file, Affinity Publisher 2 crashes instantly and generates no crash log at C:\Users\<username>\.affinity\Publisher\2.0\CrashReports\reports. What I expected to happen: to be able to duplicate or copy Page 4 without the program crashing.
   4. Recipe for creating the problem: In the attached file, attempt to Duplicate Page 4 or copy all of its contents.
   5. Screenshots: I haven't provided screenshots or video of the problem since it's been easy to reproduce on two separate machines, and there isn't much to show except for a sudden disappearance of the program (there is no crash message or debug pop-up if there is supposed to be one; I have not encountered other crashes before.)
   6. Unusual hardware or relevant other applications: The two machines are extremely different in hardware and software (one is a beefy home gaming PC and the other is a really weak office work PC with no hardware overlap and little software overlap) so I don't expect any specific interactions to be the culprit.
   7. Did the same thing used to work? I've been able to Duplicate or Copy other pages in the past with no problem, including within the same document. Have you changed anything recently? Not since starting to use Affinity Publisher 2, but it's been less than a week since I got this program.

Ironsworn.afpub

Edited March 23 by Mycoscopic

[MikeTO]

Hi @Mycoscopic and welcome to the forums.

I don't know why it's crashing, but it's related to the group of two objects pinned inside the Art Text object that is grouped with other objects inside a text frame. The Art Text object is providing no value, perhaps you created it accidentally, but if you drag the "Progress" group above the Art Text layer and then delete the Art Text layer, you'll be able to duplicate the page.

Good luck

 

[Mycoscopic]

Got it, thanks! In case it helps troubleshoot on the backend for future fixes, I can describe how this happened. I made that "+PROGRESS" group in the Designer Persona, and "Progress" is a Symbol which was copy-pasted into an Art Text after some text, which is the main way I add symbols. Later, I deleted the rest of the text in that text box to move it to its own layer (the + sign that's the next layer) but left the Progress Symbol behind, which is how it's still inside that Art Text.

It can't be just that though, because I have a nearly identical situation but with a different symbol happening with "+SUPPLY" near the bottom of Page 3, which duplicated just fine to what's now Page 5. I notice that during the duplication, the scale of that symbol did not duplicate correctly (the Symbol called "SupplyLight", which is two overlapped tan boxes, is a little bigger than it's supposed to be; this is easy to see when switching back and forth between the two pages). Since the Progress Symbol is itself a little bigger than the SupplyLight symbol, assuming it's also getting duplicated a bit bigger than it should be, perhaps that size is exceeding some kind of maximum threshold within its group which is causing the program to crash. Just a thought!

I'll make sure to avoid doing this in future, I've been converting this by hand from a pretty complex LaTeX file made of nested shapes and text within other shapes and text and although I'm learning I'm sure I'm not using great organizing logic for how it should work in Affinity! I can see that I'm probably pushing the complexity too high, I'll try to avoid this kind of empty nesting.

Edited March 24 by Mycoscopic