TWO Crashes on Mac When Address Lane Group Foldup is Clicked [Fixed]

Here’s the crash summary.

Occurred when I created address lanes in the Timeline and then attempted to “fold up” the TTS sub-lanes underneath by clicking the “down” arrow in the header of the address lane.


Translated Report (Full Report Below)

Process: TWO [2166]
Path: /Applications/OSC/*/TWO.app/Contents/MacOS/TWO
Identifier: com.coma.TWO
Version: 0.9.22 (0.9.22)
Code Type: X86-64 (Native)
Parent Process: launchd [1]
User ID: 501

Date/Time: 2023-05-25 12:11:29.2043 -0400
OS Version: macOS 13.4 (22F66)
Report Version: 12
Bridge OS Version: 7.5 (20P5058)
Anonymous UUID: 5DA32F41-9A4A-D1E9-637E-C13022A64D1E

Time Awake Since Boot: 5000 seconds

System Integrity Protection: enabled

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

Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000074
Exception Codes: 0x0000000000000001, 0x0000000000000074

Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [2166]

VM Region Info: 0x74 is not in any region. Bytes before following region: 140737486983052
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
shared memory 7fffffeb1000-7fffffeb2000 [ 4K] r-x/r-x SM=SHM

ID Vend/Dev
9a46 687f1002
Seconds Ago ID Type
5000.0 9a46 Attach

Thread 0 Crashed:: JUCE Message Thread Dispatch queue: com.apple.main-thread
0 TWO 0x106fa0ff3 0x106f5e000 + 274419
1 TWO 0x107211563 0x106f5e000 + 2831715
2 TWO 0x1072113f1 0x106f5e000 + 2831345
3 TWO 0x107210eb5 0x106f5e000 + 2830005
4 TWO 0x107204a4b 0x106f5e000 + 2779723
5 TWO 0x10720472c 0x106f5e000 + 2778924
6 TWO 0x107203824 0x106f5e000 + 2775076
7 TWO 0x107203878 0x106f5e000 + 2775160
8 TWO 0x107201c03 0x106f5e000 + 2767875
9 AppKit 0x7ff815dde5ea _routeMouseUpEvent + 138
10 AppKit 0x7ff81557eb83 -[NSWindow(NSEventRouting) _reallySendEvent:isDelayedEvent:] + 424
11 AppKit 0x7ff81557e7bf -[NSWindow(NSEventRouting) sendEvent:] + 345
12 AppKit 0x7ff81557d199 -[NSApplication(NSEvent) sendEvent:] + 345
13 AppKit 0x7ff815837ace -[NSApplication _handleEvent:] + 65
14 AppKit 0x7ff81540cb0d -[NSApplication run] + 623
15 TWO 0x10713687c 0x106f5e000 + 1935484
16 dyld 0x7ff811f5341f start + 1903

1 Like

Thanks! I’ll look into this one too while diagnosing and fixing the recording bug you reported.