Hi, Just installed on a Windows 11 machine with pretty robust specs and for some reason Live crashes every time I drop in OSC/PAR.
Happy to provide any documentation to help resolve this issue.
1 Like
Looks like I’m having the same issues with same version but on Mac (ARM). Wasn’t happening before so might be a new update thing.
So its a new crash caused by the new version of Ableton? I’ll have to try and reproduce. It may be worth reporting to Ableton as well, since this VST has been stable in previous versions and in other apps…
Having the same problem after updating to Ableton 11.3.2 all is fine until I try to load OSC/Par, when I do Ableton crashes, any fix for this?
I think for now you’ll have to downgrade. Offhand it does seem like an Ableton bug, since it’s never been an issue before.
like downgrade to an older version of OSC par or downgrade to an older version of ableton?
The previous version of Ableton, what were you using before where it was working? I assume it’s this sub-update that introduced this regression.
Hey 
I have OSC/PAR crashing Ableton 11.3.3 … Wasn’t sure how to downgrade to 11.3.2 but in 11.2 it seems to be fine. Are you planning to fix the bug that is making it crash in the Ableton update?
Pasting the crash report below, maybe it’s of use.
"Termination Reason: Namespace SIGNAL, Code 11 Segmentation fault: 11
Terminating Process: exc handler [1614]
VM Region Info: 0 is not in any region. Bytes before following region: 4364746752
REGION TYPE START - END [ VSIZE] PRT/MAX SHRMOD REGION DETAIL
UNUSED SPACE AT START
—>
__TEXT 10428c000-108b68000 [ 72.9M] r-x/r-x SM=COW …ts/MacOS/Live
Thread 0 Crashed:: MainThread Dispatch queue: com.apple.main-thread
0 OSCpar 0x3ae1b3584 juce::TextEditor::setText(juce::String const&, bool) + 40
1 OSCpar 0x3ae2c42c0 std::__1::__function::__func<EA::GUI::StringEditor::StringEditor()::$_2, std::__1::allocatorEA::GUI::StringEditor::StringEditor()::$_2, void ()>::operator()() + 56
2 OSCpar 0x3ae2c42c0 std::__1::__function::__func<EA::GUI::StringEditor::StringEditor()::$_2, std::__1::allocatorEA::GUI::StringEditor::StringEditor()::$_2, void ()>::operator()() + 56
3 OSCpar 0x3ae27a7a8 juce::MessageQueue::deliverNextMessage() + 288
4 OSCpar 0x3ae27a648 juce::MessageQueue::runLoopSourceCallback(void*) + 32
5 CoreFoundation 0x1b54a5044 CFRUNLOOP_IS_CALLING_OUT_TO_A_SOURCE0_PERFORM_FUNCTION + 28
6 CoreFoundation 0x1b54a4f90 __CFRunLoopDoSource0 + 208
7 CoreFoundation 0x1b54a4cf4 __CFRunLoopDoSources0 + 368
8 CoreFoundation 0x1b54a3610 __CFRunLoopRun + 828
9 CoreFoundation 0x1b54a2b34 CFRunLoopRunSpecific + 600
10 HIToolbox 0x1be0e2338 RunCurrentEventLoopInMode + 292
11 HIToolbox 0x1be0e20b4 ReceiveNextEventCommon + 564
12 HIToolbox 0x1be0e1e68 _BlockUntilNextEventMatchingListInModeWithFilter + 72
13 AppKit 0x1b800a51c _DPSNextEvent + 860
14 AppKit 0x1b8008e14 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 1328
15 AppKit 0x1b7ffafe0 -[NSApplication run] + 596
16 Live 0x105338bb0 0x10428c000 + 17484720
17 dyld 0x10adc508c start + 520"
Currently it seems like the crash is caused by a change to Ableton. It’s not a bug in the plugin itself (since it works in all other software and Ableton versions).