AD v2.1.1 MacOS: Malformed embedded image file causes app crash upon opening

[purplie]

Summary: The attached SVG file crashes Affinity Designer upon opening.  It has an embedded malformed PNG image.

Application:  Affinity Designer 2.1.1

OS: MacOS 13.5

Reproducable: Yes

tink.svg

[Hangman]

Hi @purplie,

Most likely because the png in the file is linked rather than embedded, something which Inkscape supports. I realise this relates to your other post about linking files in SVG exports but Affinity apps don't currently support this.

Having said that, I would have expected Designer to open the file and but as a blank page because it can't locate the external png, as other Vector apps do.

 

 

[purplie]

The attached sample file includes an embedded (corrupt) image, not a linked one.

[Hangman]

2 minutes ago, purplie said:

The attached sample file includes an embedded (corrupt) image, not a linked one.

Maybe that's why it's crashing Designer if the embedded file is corrupt... What is your expectation when opening the file or is it more to highlight that it crashes Designer?

[purplie]

It's to highlight the crash.  (Obviously I don't expect it to read a bad file.)

I lost some other open files that hadn't been saved yet, because when AD restarts, and asks you whether to 'Restore unsaved files', if you say Yes, it'll just crash again trying to reopen the bad file.

Also, if bad input causes a crash, it can be a sign of a security vulnerability, if it's caused by a buffer overflow or something like that.

[Hangman]

Ah, okay, that makes more sense now, hopefully, someone from the moderation team can comment since your file opens in other apps without them crashing...

[Lee D]

I've logged the file with the developers to take a look to see if how an embedded corrupt file is handled can be improved or to prevent a crash.

[Affinity Info Bot]

The issue "SVG crashing app when Opening/Placing" (REF: AF-286) has been fixed by the developers in internal build "2.4.0.2185".
This fix should soon be available as a customer beta and is planned for inclusion in the next customer release.
Customer beta builds are announced here and you can participate by following these instructions.
If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us.