Pauls

Hi @Pauls,
exactly there is a grouped running header with shaped object.

@Pauls All 4 zipped packages uploaded. 
Test Page: always open, never an issue (was back a few versions when linked eps caused issues) A4 Advert: Can work, open, close, quit with this one no problem, and works fine even with Editorial and Test Page open. Editorial: Same as the A4 Advert doc. Vital: This is the one that is most suspect. When it is open with the others, will eventually freeze at closing or quit. Happens every time. That said, it can be closed if done within seconds of opening. But if a little time passes, will freeze the app every time.

Hi @Pauls,
please find the logs (crash report and console log) attached. This recent crash happend while I'm insert an asset (picture frame).
Cheers
Jan
crashlog.txt console_log.txt

@Pauls thanks a lot. I uploaded the file and a and a short screen record, so you can see the behavior.

Good news everyone in this thread, I've finally replicated it! Key part is to undock the Layers Panel after placing the image.  I always have my Layers Panel floating, so thought that was all that was needed.
Thanks @Gaal Dornikand @Ron P.for your help in this thread, I'll get this logged with the Developers  
@carl123Thanks for the extra information, I'll add that to the report. 

In attach, a "crash sample file" and my spelling folder.
Thank you very much @Pauls.
 
 
fr-FR.zip facture.afpub

Compared to the bloated clunky UI of Photoshop it is a triumph IMO

@Pauls The help search field disappeared for me today in Publisher 2.1 beta 1806. I don't know what the trigger was because I'd had the app open a long time in the background, and after restarting I couldn't duplicate it.
I googled the issue and found reports of it with ID, too. Some users seem to encounter this more frequently and one shared a solution which was to use System Settings > General > Language & Region and then to explicitly specify the language for the app rather than relying on the system default language. I can't replicate the problem so I don't know if this actually does anything but maybe it's a clue. But in any case, it sounds like this isn't a bug with Affinity and can be chalked up to a macOS issue.

You can, you set it in the Develop Assistant... then once you've made all your adjustments in the Develop Persona and click Develop you will end up with a 16 bit image...

It seems the version 2.1 fixes this issue!

The whole package is quite complex, but here are few rules of thumb whenever placing PDF content and exporting to PDF, and PDF/X is involved either in export or placement:
1) If there is placed content using PDF/X-1a or PDF/X-3 (which are version 1.4 when produced from within Affinity apps), you need to export using PDF/X-3 or PDF/X-4, or any non-PDF/X-based method, to not cause rasterization / translated color values (e.g. rich black).
2) If there is placed content using PDF/X-4 (which is version 1.6), you need to export using PDF/X-4, or any non-PDF/X-based method using PDF version 1.6 or later, to not cause rasterization / translated color values (e.g. rich black). 
3) If there is non-PDF/X-based placed content, you need to export using non-PDF/X-based method using the same or later PDF version than a placed PDF content, to not cause rasterization / translated color values (e.g. rich black). The most compatible choice would then be PDF 1.7. Whatever the non-PDF/X-based choice used, live transparencies (opacity values and blend modes) would not be flattened (because Affinity apps do not support PDF version 1.3, which would cause flattening). In Affinity apps transparency flattening is only used in PDF/X-1a and PDF/X-3. 
4) Placing PDF as interpreted causes failure to read the overprint status of native objects. Also, if the files use embedded CMYK profiles and there is a conflict with the export target, or if the files do not use embedded CMYK profile and the document working profile (as defined in Preferences) that these files will be assigned with, and there is a conflict with the export target, CMYK color values of the placed PDF content will be translated at export time. This basically corresponds a situation where non-document CMYK profile is defined at export time. Letting Affinity apps interpret the placed content may also result in failure to map fonts (even when they are installed on the system), especially if the PDFs have been created with non-Affinity software (e.g. Adobe apps or CorelDRAW), even on the same computer. 
Here are demo files:
a) Miscellaneous placed PDF content exported using PDF/X-1a (all placed content will be rasterized):
 pdfxcompatibility_pdfx1.pdf
b) Miscellaneous placed PDF content exported using PDF/X-4 (non-PDF-based content will be rasterized):
pdfxcompatibility_pdfx4.pdf
c) Miscellaneous placed PDF content exported using non-PDF/X-based PDF1.7 (note that Adobe Acrobat Pro shows the color values of the non-PDF/X-based PDF at the lower left corner incorrectly; the true color values are shown using the Object Inspector of the Output Preview dialog box):
pdfxcompatibility_pdf17.pdf
d) Example of an export file (PDF/X-4) using interpreted placed PDFs (note the lost overprints):
pdfxcompatibility_pdfx4_interpreted.pdf
A couple of further notes:
Affinity apps always convert RGB values of native objects (shapes and text) to CMYK, also when using PDF/X-3 or PDF/X-4 which allow RGB definitions (this is unlike e.g. InDesign). Additionally, PDF/X-3 also converts image color spaces to CMYK, disregarding the value of "Convert image color spaces" setting...[EDIT: After rechecking, this only seems to happen if there is need for transparency flattening, and InDesign does behave here similarly.] When using PDF/X-1 or PDF/X-3, all transparencies are flattened by using rasterization instead of Boolean operations (which are tried to be used when exporting from Adobe apps or QuarkXPress). A long story short: Export using PDF/X-4 (while having the content placed to be passed through), or using non-PDF/X-based version 1.7, and if using the latter, remember to uncheck the "Embed ICC profiles". The latter will keep placed non-PDF/X-based content unchanged, the former will not. In both cases, your export files will contain live transparencies, in case not flattened in the placed document or on the canvas. If you need to export transparency flattened PDF/X-1a content and you have them in placed PDF/X-4 content, you are out of luck. That means: the content will be rasterized unless you can flatten it in the source files and reproduce.
Note: These tests and files have been created using the 2.0.4 Windows version of Affinity apps, but versions 1.10.6 and the latest v2 beta behave similarly, on both Windows and macOS.
 

After more testing on new photos I am impressed at the performance. Yes it is what I would call slow but that is not Affinity, it is the slow computer. I was able to work faster than with 2.0 without the not responding issue and even with a 12 image pano (total size of the 12 files 300mb) and creating a 650 .afphoto file it was quicker than I expected.

Even a 21photo (total 800mb) pano worked as expected. Bearing in mine a single photo was crashing 2.0 last week after the Windows update this is a fantastic result.

So from me it is a WELL DONE SERIF.
 

I can recreate this so I'll get it logged - looks like some sort of thread locking problem

Works perfectly on v2.1.0 (latest release)--thank you very much!

Hi,
just some compliments on the release notes for 2.1. Very well designed and presented, this is how release notes should be made. Usually, it is boring list of stuff nobody wants to read. It is obvious that you put a lot of effort into that, was worth it!
Cheers,
Lars

@Pyanepsionwe think we'll get this fixed for 2.2

@Pyanepsionwe think we'll get this fixed for 2.2

My favourite as a kid with its art deco looks and having the speed record of 126mph. Back then I didn't realise it was one of a quite a few class A4's. Designed by Nigel Gresley and built in 1938 by London & North Eastern Railway in Doncaster.
I'll likely shrink it down a bit so there's more sky above the funnel but have left it like that for now so it's easier to work on and see the details.
The outline's without the background otherwise it looks even more of a mess.

Having the keyboard input set to romanji would appear to be the key to this crash

No, it shouldn't, I used to be on insider build in the past but some problems made me opt out and I'm back to the normal version.

new issue raised for this

The disappearing window is a bug I've added your report to the issue

Uncheck Import PSD Smart Objects Where Possible in the General preferences and the file will open correctly.

https://github.com/dortania/OpenCore-Legacy-Patcher/releases/0.6.3 has the following:
Resolve 3rd Party Apps erroring on Metal with macOS 13.3 Applicable Software: Applications directly using Metal (ex. Blender, Parallels Desktop) Applicable Hardware: 3802-based GPUs (ie. Intel Ivy Bridge and Haswell iGPUs, Nvidia Kepler dGPUs) Installed 13.3.1 and OCLP 0.6.3 and Affinity Photo 2.0.4 is running fine again  🚀