FabFilter User Forum

Pro-Q3 causes weird crash in logic on latest systems..

Hi! I've been using fabfilter for a while now and never seen any issues with it until the latest week - I haven't updated any OS or Logic - running latest of everything on the newest fastest MBP 16". All of a sudden these crashes started happening, here are the details. Anyone else who has seen the same issues?

Process: Logic Pro X [2395]
Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X
Identifier: com.apple.logic10
Version: 10.4.8 (5182)
Build Info: MALogic-5182000000000000~3 (10S138)
App Item ID: 634148309
App External ID: 833082327
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Logic Pro X [2395]
User ID: 501

PlugIn Path: /Library/Audio/Plug-Ins/Components/FabFilter Pro-Q 3.component/Contents/MacOS/FabFilter Pro-Q 3
PlugIn Identifier: com.fabfilter.Pro-Q.AU.3
PlugIn Version: 3.11 (3.11)

Date/Time: 2020-02-29 12:37:04.568 +0100
OS Version: Mac OS X 10.15.3 (19D76)
Report Version: 12
Bridge OS Version: 4.2 (17P3050)
Anonymous UUID: xxxx


Time Awake Since Boot: 550 seconds

System Integrity Protection: disabled

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

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [2395]

Application Specific Information:
MALondonIII | 64afe96199c0abb536d1562f0b96493eb3eade7adf2dc2a56ac920c93aeb2acd | 997ecf0fd6b52f8054dac84604e944090b0e1f49 | 2019-11-28_11:08:05

Anton

Hi Anton,

Please drop us a line at info@fabfilter.com and we'll get you sorted!

Cheers,

Ralph (Fabfilter

Hi guys,

is there a fix so far? Have the same problem with latest Logic and FF versions. Crushes at starting Logic.

Let me know, if you need a bug-report?!

Please help,

Best - Luke

Luke

Hi Luke,

Please drop us a line at info@fabfilter.com if you have the same problem!

Cheers,

Ralph (FabFilter)

I got, I guess, the same problem. Logic session doesnt start anymore...Please help...

Tobias Mertens

Hi Tobias, please drop us a line at info@fabfilter.com

Cheers,

Ralph (FabFilter)

For other who are experiencing this issue:

It seems to be caused by the PACE framework, as used by iLok-protected plug-ins from companies such as SoundToys or Slate. These plug-ins seem to occasionally corrupt the memory space of other plug-ins like ours.

We're working on a workaround to at least avoid crashes until PACE fixes this. We have test versions for Pro-Q 3 and Pro-MB with this workaround; please e-mail us at info@fabfilter.com so we can give you access to these.

Floris (FabFilter)

Short update: we have now created a macOS pre-release for a minor update of all plug-ins, which should fix the issues above.

If you are experiencing crashes with Pro-Q 3 or other FabFilter plug-ins, in combination with iLok protected plug-ins (e.g. Sound Toys, Slate, etc.), for example when loading Logic Pro X sessions, please try the following macOS pre-release (64-bit only) installer:

www.fabfilter.com/download/pre-release/fftotalbundle.dmg

Note: during installation, you can choose 'Customise' to select the plug-ins you would like to install.

IMPORTANT: This is an untested pre-release, which might still contain minor issues or small bugs. If you encounter any problems, do let us know of course!

Floris (FabFilter)

Thanks for this! I was experiencing the same issue and tried countless times to open a project with multiple instances of Pro-Q 3 and it crashed every time.

After installing this pre-release it seems to be working fine!

Ryan Callahan

Hi dear people at FabFilter,

Logic crashes sometimes when I insert FabFilter Pro-R, especially when I insert the plugin during playback.

I do not use iLok.

Here is the latest crash report:

Process: Logic Pro X [958]
Path: /Applications/Logic Pro X.app/Contents/MacOS/Logic Pro X
Identifier: com.apple.logic10
Version: 10.4.8 (5182)
Build Info: MALogic-5182000000000000~3
App Item ID: 634148309
App External ID: 833082327
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Logic Pro X [958]
User ID: 501

Date/Time: 2020-04-17 17:19:06.419 +0200
OS Version: Mac OS X 10.14.6 (18G4032)
Report Version: 12
Anonymous UUID: D9E7B532-95C0-BE4D-F0F1-5832AFFB2404

Sleep/Wake UUID: 96759C2C-0B00-42DA-866B-720ECFE7AAA4

Time Awake Since Boot: 9800 seconds
Time Since Wake: 890 seconds

System Integrity Protection: enabled

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

Michael K

Hi Michael,

The crash log you posted did not show a crash in Pro-R, but in Logic Pro X itself. This doesn't necessarily mean that Pro-R isn't the cause, but rather that the crash log doesn't give any information to us.

Have you tried the latest pre-release of Pro-R (version 1.07)? Please download this installer:

www.fabfilter.com/download/pre-release/fftotalbundle.dmg

Note: during installation, you can choose 'Customise' to select the plug-ins you would like to install.

IMPORTANT: This is an untested pre-release, which might still contain minor issues or small bugs. If you encounter any problems, do let us know of course!

Floris (FabFilter)

Thanks, Floris. Highly impressed by how you take care of your clients.

Michael K

Thanks, Floris. Highly impressed by how you take care of your clients.

Michael K

Hi, I'm also a FabFilter customer (I bought the total bundle) and I'm pleased to see how helpful your support is! I never knew since I never had any problem or crash with your fine plugins. You quickly recognized the issue and released a fix. However I'm writing because I have the same crashes, with the very same crash log details, when opening Logic Pro X with another plugin: reFX Nexus.

System Integrity Protection: enabled

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

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY

Termination Signal: Trace/BPT trap: 5
Termination Reason: Namespace SIGNAL, Code 0x5
Terminating Process: exc handler [25364]

Application Specific Information:
/Library/Audio/Plug-Ins/Components/Nexus.component/Contents/MacOS/Nexus
MALondonIII | 64afe96199c0abb536d1562f0b96493eb3eade7adf2dc2a56ac920c93aeb2acd | 997ecf0fd6b52f8054dac84604e944090b0e1f49 | 2019-11-28_11:08:05

reFX support is telling me that they don't use PACE—but neither does FabFilter—and their last word is that I'm the only one with the problem and they can't reproduce it (obviously since you need to load in memory the same large amount of plugins called by my project which they don't have installed) which I can translate to: it's your problem not ours. (If I had known I wouldn't have spent hours trying to document the issue and sent them dozens of test files and crash logs).

Also, PACE support has yet to answer to me. So the last chance for me to convince them that there is an issue with PACE corrupting the memory of other plugins and locking people out of their projects, is that you explain to me what your fixes consist of and how it is possible to circumvent this corruption.

Best,
Ed

Ed

Hi Ed!

So the crash log you just posted is about a crash in reFX nexus, right? Could you send us the full crash log via e-mail, and maybe connect us with the reFX nexus devs as well?

Thanks!

Floris (FabFilter)

Thanks a lot Floris, I have sent all the crash logs to info@fabfilter.com
Your support is stellar, it goes all the way and beyond!
I'm glad I got the full bundle from you.

Ed

Hi there,

I'm also an ilok user getting the exact same issue being described here,

Does anyone know if there's a fix for this available for other plugins?

Ellis Clarke

Hi Ellis,

This is a known issue, which seems to be caused by the PACE framework, as used by iLok-protected plug-ins from companies such as SoundToys or Slate. These plug-ins seem to occasionally corrupt the memory space of other plug-ins like ours.

We've implemented a workaround to at least avoid crashes until PACE fixes this. Here's a Total Bundle pre-release (64-bit only, to be officially released very soon), which contains plug-in versions that should work properly:

www.fabfilter.com/download/pre-release/fftotalbundle.dmg

Note: during installation, you can choose 'Customise' to select the plug-ins you would like to install.

Let us know if this fixes your issue!

Cheers,

Ralph (FabFilter)

Hi Ralph thanks for your help,

Do you have any idea when PACE might issue a fix for this as it's not just FF related for me, I have issues with UAD plugins, waves, Hoser etc..

Ellis

Hi Ellis,

Unfortunately we do not, but we hope soon :-)

Cheers,

Ralph (FabFilter)

Useful work around -

Open new session and open the offending plugin on a new audio track. This seems to rebuild the framework. Then open your session - worked for me...

Tom Andrews

Wow thanks Tom! That worked for me as well, very easy fix (:

Tristan

Unsure whether this is related, but I bought the pro bundle for iPadOS, using in GarageBand. The crashing started with any FF AU on direct launch of the FF app, and GarageBand says they’re not installed (they are).

Chris Lorensson

No problems with plugins. Have you activate Rosetta. ?

Steflamenco

My Mac Pro running Mojave is crashing when I add a single instance of Q3.. which makes very little sense. Please advise

Jeff

hi Jeff, could you tell us a bit more about your system? What DAW? What plug-in version? When do the crashes occur?

Ralph Verdult (FabFilter)

Reply to this topic: