Photo on MacOS quits 'unexpectedly'

[Tearlach]

So having struggled for days with terrible crashes on my Windows installation (and happy that my Mac version was still working), today Photo 1.10 (official release) quit unexpectedly in background. It offered to recover open files, but failed. Then it crashed again the same way. It's now running, but I have two crash reports to post from the Console crash log.

This is a new M1 MacBook Air 16GB RAM 1TB SSD storage.  OS data is in the crash logs.

Affinity Photo_2021-08-18-171834_MacBook-Air.crash Affinity Photo_2021-08-18-171900_MacBook-Air.crash

[MEB]

Hi @Tearlach,
Welcome to Affinity Forums
The crash seems related to issues loading an asset. Have you added any assets there recently? Did the app crashed when you opened/loaded the Assets panel or switch to it from another tab?

[Tearlach]

Sorry, I guess I was fairly concise when I said "in background".

What precipitated (or "coincided with" might be more accurate) the event was attempting to open a file that I had been emailed (a black-and-white bitmapped PDF file of a scanned document). I used the old: right-click, "Open with...", "Affinity Photo"... from within the Mail app - directly on the attachment. I did not save the file to a new location first.

Affinity Photo was running in background at the time - with a couple of documents (edited but not saved) open.

I can't recall the precise sequence of events that followed, but the scanned document never opened and Photo "quit unexpectedly".

Then ensued a strange sequence I've never seen. I asked it to reopen (standard system dialog box) and in the process Affinity Photo opened TWO separate terminal windows (in background) in which a series of commands and responses appeared.  I'm afraid I did not save those transcripts.  One of them said something about clearing scratch space or flushing caches or the like (I paraphrase, but that was the gist)

Affinity Photo did attempt to reopen. It asked if I wanted to recover documents. I said "yes", and it crashed hard again (quit unexpectedly). That's the second crash report above, about 1 minute after the first.

I don't believe that it opened the terminal again this time, but I did request it to reopen again (from the system dialog that asks), just to see what would happen.

The 2nd time it did reopen successfully... unfortunately asking about recovering documents - unsuccessfully.

It's actually been running since then (about 15 hours, overnight) without another crash. It hasn't been doing much work. Mostly it's been in background with that B&W file open (and edited). It did edit that document for me successfully. It did NOT manage to recover work from the previously open documents.

-charlie

[Tearlach]

I can open a new thread if needs be, but the topic title here is still correct. The conditions were different.

Affinity Designer 1.10.1 "quit unexpectedly" while I was attmempting to paste a style from one rectangle (with gradient fill) to 6 other (identical) rectangles elsewhere in the drawing.  It stumbled. Then it hung. Then BANG it was gone.

It did manage to open its 'recovery file' this time, but it did not recover all of my work.

Same machine as above. Only updated Designer when the last commercial release appeared.

Crash log below.

Affinity Designer_2021-08-31-094238_MacBook-Air.crash

[Tearlach]

Sorry - I just realized that my original report was for Photo... and this crash was designer. I flip back and forth so often that I got lost. It should probably go in a different thread. Mea Culpa.