Fender Studio Pro 8.0.2 - Discussion Thread

[Number6]

A workaround is to use the online help at FSP8 Manual.

Yup. It's just an example.

 

[Number6]

8.0.3 now out. Clearly a major bug fix only release/tidy up.

I expect the demo version to be around the corner too. Next stop 8.1.0 unless there is a serious flaw in this one.

Version 8.0.3 Release Notes (March 24, 2026):

The following issues have been fixed:

• [macOS] Potential crash when loading certain Track Presets

• [Windows] Non-High-DPI Mode broken

• [Linux] Potential crash/freeze when dragging effects

• [Pro EQ³] True Peak level altered when active

 

[id4fsp]

looking forward for 8.1.0

 

[Mdnolan]

Just checking if anyone has been having the same problem - getting regular crashes on Mac mini m4pro - Tahoe latest version. Seems to be associated with any typing (eg searching for plugins and other keyboard inputs. Have had the crash reports analysed by Claude - basic message is:
Crash #1 (May 22): Triggered by typing — keyDown → insertText → NSTextContentStorage → crash
Crash #2 (May 20): Triggered by clicking to rename something — mouseDown → NSTextField becomeFirstResponder → selectText → sizeToFit → NSTextLayoutManager → crash
The trigger differs but the destination is the same broken code path in UIFoundation's text layout system. This tells you:

Any interaction that activates a text field in Studio Pro can trigger this crash — whether you're typing or just clicking on a text element to select/rename it.

Session Length Pattern​

Crash	Launch	Crash	Duration
May 20	15:23	19:02	~3.5 hours
May 22	08:58	19:15	~10.3 hours

The May 20 crash happened after only 3.5 hours — so this isn't purely a long-session memory leak. The memory allocation failures are happening relatively quickly too. Something more systematic is going on.

Revised Assessment​

The consistent mach_vm_allocate_kernel failed pattern across both crashes, at different session lengths, points more strongly to a virtual memory address space exhaustion or fragmentation bug in cclgui rather than a simple slow leak. The cclgui UI layer appears to be fragmenting the VM address space over time — and when macOS's text layout system then tries to allocate memory to handle a text field interaction, there's no contiguous space left.
This is essentially a cclgui memory management bug that makes the app progressively more fragile with use, and Apple's Tahoe text stack (which is less forgiving about memory than the old NSLayoutManager) is what ultimately falls over.

What This Means Practically​

• The 3.5 hour crash is the important data point — you can't work around this just by restarting every few hours; 3.5 hours isn't a viable session limit in a DAW
• Renaming tracks or clicking text fields is a reliable trigger — try to minimise text field interactions during sessions
• This needs a fix from Fender/PreSonus — you should report both crashes together as they strengthen the case considerably

Any comments - similar experiences?

 

[Mdnolan]

Just to add I’m on the latest version 8.03