Jump to content
You must now use your email address to sign in [click for more info] ×

Affinity on Mac crashes every time FFT filter runs


Recommended Posts

Welcome to the forum abkaye, 

What Operating System are you using?

Could you upload the image you are using when it crashes so we can test it our end?

iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9  
B| (Please refrain from licking the screen while using this forum)

Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions

Link to comment
Share on other sites

FFT is working for me in the current retail version of AP 1.7, even with your provided image.
I’m on OS Mojave still, so that may be a factor?

macOS 10.15.7  15" Macbook Pro, 2017  |  4 Core i7 3.1GHz CPU  |  Radeon Pro 555 2GB GPU + Integrated Intel HD Graphics 630 1.536GB  |  16GB RAM  |  Wacom Intuos4 M

Link to comment
Share on other sites

Yep working fine on High Sierra too.

iMac 27" 2019 Somona 14.3.1, iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9  
B| (Please refrain from licking the screen while using this forum)

Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions

Link to comment
Share on other sites

I tried it a few times (using Catalina) and a couple of times it was fine and a couple of times it shut Affinity Photo down instantly.

The error report was huge (and gobbledygook!).

I think it's probably a Catalina thing - sometimes I'm wishing I'd never "upgraded"!

This means nothing to me but it might mean something to someone:

Crashed Thread:        0  Dispatch queue: com.apple.main-thread

Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
Exception Codes:       KERN_INVALID_ADDRESS at 0x0000000000000018
Exception Note:        EXC_CORPSE_NOTIFY

Termination Signal:    Segmentation fault: 11
Termination Reason:    Namespace SIGNAL, Code 0xb
Terminating Process:   exc handler [7825]

VM Regions Near 0x18:
 

Edited by Geoff777
added a bit from crash report
Link to comment
Share on other sites

2 hours ago, Chris B said:

Hi Geoff777,

I managed to get it once (as did a colleague) but I've got a full crash report so I'll submit this to the development team. 

Hi Chris,

That's good.... I didn't post the full report because..... ZZZZZZZ!

Sure it's cached somewhere if you need a copy.

Cheers

Link to comment
Share on other sites

  • 4 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.