Crash in Scaler 3.2.1 when using ‘Add to Progression’ in Ableton Live 12.3.6 on macOS, causing Live to terminate with a segmentation fault.

Scaler 3 Support Bug Reports
,
1

Hi,
I’m experiencing a repeatable crash of Scaler 3.2.1 when using the “Add to Progression” function inside Ableton Live.

Environment

  • Scaler version: 3.2.1

  • DAW: Ableton Live 12.3.6 (Suite)

  • OS: macOS 26.4 (ARM, Apple Silicon)

  • Plugin format: VST (loaded in Ableton’s VST folder)

Steps to reproduce

  1. Create a MIDI track in Ableton Live 12.3.6.

  2. Load Scaler 3.2.1 on that track.

  3. Detect/choose a scale and chords as normal.

  4. Right‑click an individual chord and choose “Add to Progression” (or the equivalent menu entry that appends/duplicates clips at the end of the track).

  5. As soon as the action is triggered, Ableton Live immediately crashes.

Observed behavior

  • Live quits instantly with a segmentation fault (EXC_BAD_ACCESS / SIGSEGV).

  • The macOS crash report shows the crash on the main thread, inside Scaler’s sequencer code when handling the chord menu action.

  • After the crash, reopening the same project and repeating the operation causes the same behavior.

Relevant portion of the crash report
On the main thread I see:

  • Exception Type: EXC_BAD_ACCESS (SIGSEGV)

  • Exception Subtype: KERN_INVALID_ADDRESS at 0x0000000000000118

Backtrace excerpt (thread that crashed):

  • Scaler::Core::Sequencer::Track::getClipLength(unsigned int) const

  • Scaler::Core::Sequencer::copyClipsAtEndOfTrack(...)

  • Scaler::UI::Components::ChordComponent::handleMenu(int)

This looks like Scaler is trying to access a clip length from an invalid or null object when duplicating/adding clips at the end of the track as part of the chord menu action.

I have attached the complete macOS crash report file (Scaler3_AbletonLive12_crash_report.txt) so you can see the full backtrace and system details.

Scaler3_AbletonLive12_crash_report.txt (192.8 KB)

2

Welcome to the community @mirco And thanks for the report. I can’t reproduce this following your steps, I am on exactly the same setup except for OS: macOS 26.4 (I’m on 15.7.5 Sequoia). We have Scaler 3.2.2 coming out within a week. I wonder if installing it, restarting your Mac and opening a vanilla session will resolve your issue? @Tristan Can you try on your end?

1 Like
3

Hey @davide no problem :slight_smile:

Today I’ve not yet the same error but a different one. The stacktrace in attachments.

paste.txt (281.1 KB)