Forums > Jitter

jit.buffer~ crash when changing buffer~

October 18, 2010 | 3:55 pm

I have a bad & reproducible crash when trying to change jit.buffer~ reference buffer~ with a "set" message.
I know that the usage such a message with this object is not documented, … but the doc says :
"feel free to use all of the friendly buffer~ messages you know and love" so I assume that it is supposed to work…

please open patch bellow to see what I mean :

– Pasted Max Patch, click to expand. –

[Max 5.1.5 / macos 10.6.4 / macpro Quad-Core Intel Xeon]

and a crash log :

Process: MaxMSP [31465]
Path: /Applications/Max5/MaxMSP.app/Contents/MacOS/MaxMSP
Identifier: com.cycling74.MaxMSP
Version: 5.1.5 (43290) (5.1.5)
Code Type: X86 (Native)
Parent Process: launchd [479]

Date/Time: 2010-10-18 17:23:37.649 +0200
OS Version: Mac OS X 10.6.4 (10F569)
Report Version: 6

Interval Since Last Report: 1801981 sec
Crashes Since Last Report: 72
Per-App Interval Since Last Report: 1468799 sec
Per-App Crashes Since Last Report: 40
Anonymous UUID: E94BD3F6-E7B2-45AE-9DBE-3C4892F5CE69

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000002f0008f
Crashed Thread: 0 Dispatch queue: com.apple.main-thread

Error Formulating Crash Report:
*** -[NSCFDictionary setObject:forKey:]: attempt to insert nil value (key: ExecutablePath)
0x80418ca6
0x885210f3
0x80418ae7
0x80418a74
0x85b58a9b
0x00004ae8
0x868b0d11
0×00004939
0x000072f2
0x00007dd7
0x00009ff2
0x00009dcf
0x8594b860
0x000094d6
0x8593f456
0x8593f309

Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 ??? 0x1636b8e7 max_jit_buffer_viz_collect + 3054
1 ??? 0x1636c42d max_jit_buffer_viz_hist_output + 367
2 ??? 0x1636c4dc max_jit_buffer_viz + 131
3 ??? 0x1636c5b6 max_jit_buffer_viz_repopulate + 137
4 com.cycling74.MaxMSP 0x0002a59b sched_dequeue + 119
5 com.cycling74.MaxMSP 0x000123e9 max_tick + 77
6 com.cycling74.MaxMSP 0x001e395c maxapplication_eventtimerproc(__EventLoopTimer*, void*) + 22
7 com.apple.CoreFoundation 0x9491670b __CFRunLoopRun + 8059
8 com.apple.CoreFoundation 0×94914094 CFRunLoopRunSpecific + 452
9 com.apple.CoreFoundation 0x94913ec1 CFRunLoopRunInMode + 97
10 com.apple.HIToolbox 0x990b2f9c RunCurrentEventLoopInMode + 392
11 com.apple.HIToolbox 0x990b2d51 ReceiveNextEventCommon + 354
12 com.apple.HIToolbox 0x9923b1e3 ReceiveNextEvent + 83
13 com.cycling74.MaxMSP 0x002d1d52 juce::juce_dispatchNextMessageOnSystemQueue(bool, bool) + 554
14 com.cycling74.MaxMSP 0x002db927 juce::MessageManager::dispatchNextMessage(bool, bool*, bool) + 79
15 com.cycling74.MaxMSP 0x002db9e6 juce::MessageManager::runDispatchLoop() + 42
16 com.cycling74.MaxMSP 0x002da341 juce::JUCEApplication::main(juce::String&, juce::JUCEApplication*) + 605
17 com.cycling74.MaxMSP 0x002da41b juce::JUCEApplication::main(int, char**, juce::JUCEApplication*) + 125
18 com.cycling74.MaxMSP 0x001e3da0 main + 76
19 com.cycling74.MaxMSP 0x00005a3e _start + 216
20 com.cycling74.MaxMSP 0×00005965 start + 41

Mathieu


October 18, 2010 | 4:12 pm

..I even managed to completly freeze my macbook pro with this patch :
(kernel panic ?)

[attachment=143898,1253]

Attachments:
  1. IMG_1019_2.jpg

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