abkaye Posted January 26, 2020 Posted January 26, 2020 Maybe it's because this is a trial version, but it's not a good sign that Affinity crashes every time I try to run the FFT filter. Suggestions? Quote
firstdefence Posted January 26, 2020 Posted January 26, 2020 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? Quote iMac 27" 2019 Sequoia 15.0 (24A335), iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 (Please refrain from licking the screen while using this forum) Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions
abkaye Posted January 26, 2020 Author Posted January 26, 2020 I'm running Mac OS 10.15.2 (Catalina). The image on which I'm working is attached. Scan034.tif Quote
markw Posted January 26, 2020 Posted January 26, 2020 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? Quote macOS 12.7.6 | 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
firstdefence Posted January 26, 2020 Posted January 26, 2020 Yep working fine on High Sierra too. Quote iMac 27" 2019 Sequoia 15.0 (24A335), iMac 27" Affinity Designer, Photo & Publisher V1 & V2, Adobe, Inkscape, Vectorstyler, Blender, C4D, Sketchup + more... XP-Pen Artist-22E, - iPad Pro 12.9 (Please refrain from licking the screen while using this forum) Affinity Help - Affinity Desktop Tutorials - Feedback - FAQ - most asked questions
Geoff777 Posted January 27, 2020 Posted January 27, 2020 (edited) 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 January 27, 2020 by Geoff777 added a bit from crash report Quote
Staff Chris B Posted January 27, 2020 Staff Posted January 27, 2020 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. Geoff777 and Callum 1 1 Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
Geoff777 Posted January 27, 2020 Posted January 27, 2020 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 Quote
Staff Chris B Posted January 27, 2020 Staff Posted January 27, 2020 I think we should be okay for now. I'll let you know if dev request one Quote How to format a bug report | Learning Resources | List of V2 FAQs | YouTube Tutorials
Staff MEB Posted February 20, 2020 Staff Posted February 20, 2020 Hi abkaye, Geoff777, This issue should now be fixed in the latest Affinity Photo Customer Beta 1.8.0.166. Let us know if you are still able to crash it. Thanks for your report. Quote A Guide to Learning Affinity Software
Recommended Posts
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.