Forums > MaxMSP

Crash in Max 5.1.9


jic
January 19, 2012 | 12:46 am

Hello~

I’m having a semi-reproducible crash happening in a fairly complex patch that procedurally draws UI. It always happens as I press one of several [textbutton]s within a [bpatcher] that runs one of several routines at higher levels in the patch, and always gives me the same crash log. I’ve tried replacing all of the [textbutton]s with simple message boxes to see if that’s the culprit, but to no avail.

Here’s the thread that’s crashing, any insight would be *greatly* appreciated. I’ve also attached the full log to the thread. Thanks in advance.

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0×0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 com.cycling74.MaxMSP 0×00065805 outlet_bang + 845
1 com.cycling74.MaxAPI 0x00ece2e9 outlet_bang + 31
2 com.cycling74.textbutton 0x181e464c jtextbutton_int + 86
3 com.cycling74.textbutton 0x181e5921 jtextbutton_mouseup + 299
4 com.cycling74.MaxMSP 0x000bb18a object_method + 896
5 com.cycling74.MaxMSP 0x0010c59e BoxComponent::sendMouseMessage(juce::MouseEvent const&, symbol*, double, double) + 414
6 com.cycling74.MaxMSP 0x0010ca98 BoxComponent::mouseUp(juce::MouseEvent const&) + 462
7 com.cycling74.MaxMSP 0x002f8891 juce::Component::internalMouseUp(int, int, int, long long) + 541
8 com.cycling74.MaxMSP 0x00391d1e juce::ComponentPeer::handleMouseUp(int, int, int, long long) + 546
9 com.cycling74.MaxMSP 0x002d36ff juce::juce_dispatchNextMessageOnSystemQueue(bool, bool) + 463
10 com.cycling74.MaxMSP 0x002dd3df juce::MessageManager::dispatchNextMessage(bool, bool*, bool) + 79
11 com.cycling74.MaxMSP 0x002dd49e juce::MessageManager::runDispatchLoop() + 42
12 com.cycling74.MaxMSP 0x002dbdf9 juce::JUCEApplication::main(juce::String&, juce::JUCEApplication*) + 605
13 com.cycling74.MaxMSP 0x002dbed3 juce::JUCEApplication::main(int, char**, juce::JUCEApplication*) + 125
14 com.cycling74.MaxMSP 0x001e5032 main + 76
15 com.cycling74.MaxMSP 0x000059fe _start + 216
16 com.cycling74.MaxMSP 0×00005925 start + 41

Attachments:
  1. maxcrash.txt


jic
January 19, 2012 | 1:24 am

A little extra data point…

It seems like Max is getting confused regarding multiple instances of identical [bpatcher]s and figuring out who is sending what. Sometimes when I press the aforementioned buttons, the "highlight" on the [textbutton] shows up in the wrong [bpatcher] entirely.

When I press these buttons inside the patcher that the [bpatcher] is calling, everything works fine.


Viewing 2 posts - 1 through 2 (of 2 total)