Forums > MaxMSP

[bug] pattrstorage crash in Max5

June 23, 2008 | 9:10 am

On a Macbook Pro 2,4 ghz, with 10.5.3 and Max 5.02, I get a crash when firing off the "line 1." (1,2 1000) in the helpfile of pattrstorage.

First I thought I had to do it two times in arow, but now it seems to crash right after the "line 1." has finished the first time. Actually the line-object in this example doesn’t seem to go all the way to 2., but only to 1.96. Can anyone copy this?


June 23, 2008 | 9:21 am

Can’t reproduce with the 5.0.3 version of the object. If the crashing goes away when you close the client and storage windows, I suspect that the bug was fixed. If not, it still seems to be working ok for me. Maybe you have a crash report?

jb


June 23, 2008 | 9:33 am

On 23 juin 08, at 11:10, Lut Lei wrote:

> On a Macbook Pro 2,4 ghz, with 10.5.3 and Max 5.02, I get a crash
> when firing off the "line 1." (1,2 1000) in the helpfile of
> pattrstorage.
>
> First I thought I had to do it two times in arow, but now it seems
> to crash right after the "line 1." has finished the first time.
> Actually the line-object in this example doesn’t seem to go all the
> way to 2., but only to 1.96. Can anyone copy this?

Same problem here, with +/- the same setup. Max crashes 1 second after
[line] reached 1.96.
The crash log shows it’s a juce crash.

p

_____________________________
Patrick Delges

Centre de Recherches et de Formation Musicales de Wallonie asbl

http://www.crfmw.be/max


June 23, 2008 | 9:36 am

Quote: Patrick Delges wrote on Mon, 23 June 2008 11:33
—————————————————-
> The crash log shows it’s a juce crash.

That’s interesting, but not terribly useful information, because it offers no context for the concerned developer to isolate what might be causing it. Please post the entire crashlog.

Anyway, I am 98% certain that this is the window update bug which has been fixed for 5.0.3.

Jeremy


June 23, 2008 | 9:37 am

On 23 juin 08, at 11:21, Jeremy Bernstein wrote:

>
> Can’t reproduce with the 5.0.3 version of the object. If the
> crashing goes away when you close the client and storage windows, I
> suspect that the bug was fixed. If not, it still seems to be working
> ok for me. Maybe you have a crash report?

Process: MaxMSP [5771]
Path: /Music/Max5/MaxMSP.app/Contents/MacOS/MaxMSP
Identifier: com.cycling74.MaxMSP
Version: 5.0.2 (34989) (5.0.2)
Code Type: X86 (Native)
Parent Process: launchd [186]

Date/Time: 2008-06-23 11:36:33.023 +0200
OS Version: Mac OS X 10.5.3 (9D34)
Report Version: 6

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

Thread 0:
0 libSystem.B.dylib 0x959ad347 szone_malloc + 14
1 libSystem.B.dylib 0x959ad2f8 malloc_zone_malloc + 81
2 libSystem.B.dylib 0x959ad28c malloc + 55
3 com.cycling74.MaxMSP 0x0036ff7d
juce::String::createInternal(wchar_t const*, wchar_t const*) + 77
4 com.cycling74.MaxMSP 0×00370647
juce::String::String(int) + 39
5 com.cycling74.MaxMSP 0×00362459
juce::PropertySet::setValue(juce::String const&, int) + 25
6 com.cycling74.MaxMSP 0x00432b02
juce::TableListRowComp::update(int, bool) + 1506
7 com.cycling74.MaxMSP 0x004315a8
juce::TableListBox::refreshComponentForRow(int, bool,
juce::Component*) + 56
8 com.cycling74.MaxMSP 0x002b53d0
juce::ListViewport::updateContents() + 976
9 com.cycling74.MaxMSP 0x002b4648
juce::ListBox::updateContent() + 2008
10 com.cycling74.MaxMSP 0×00103861
DataViewComponent::handleNotification(object*, symbol*, void*) + 1865
11 com.cycling74.MaxMSP 0x0012298e
jdataview_compnotify(DataViewComponent*, _jdv_notifier*) + 44
12 com.cycling74.MaxMSP 0x00054cca linklist_funall + 68
13 com.cycling74.MaxMSP 0x001228cc
jdataview_notifycomponents(_jdataview*, symbol*, void*) + 50
14 com.cycling74.MaxMSP 0x00124e4d
jdataview_qfn(_jdataview*) + 41
15 com.cycling74.MaxMSP 0x000252f1 sched_dequeue + 119
16 com.cycling74.MaxMSP 0x0000f489 max_tick + 77
17 com.cycling74.MaxMSP 0x001c3d76
maxapplication_eventtimerproc(__EventLoopTimer*, void*) + 22
18 com.apple.CoreFoundation 0x936e1b3e CFRunLoopRunSpecific +
4494
19 com.apple.CoreFoundation 0x936e1cf8 CFRunLoopRunInMode + 88
20 com.apple.HIToolbox 0x93db2da4
RunCurrentEventLoopInMode + 283
21 com.apple.HIToolbox 0x93db2bbd ReceiveNextEventCommon +
374
22 com.apple.HIToolbox 0x93ef5af3 ReceiveNextEvent + 58
23 com.cycling74.MaxMSP 0×00294466
juce::juce_dispatchNextMessageOnSystemQueue(bool) + 166
24 com.cycling74.MaxMSP 0x002a3043
juce::MessageManager::runDispatchLoop() + 131
25 com.cycling74.MaxMSP 0x0029e94f
juce::JUCEApplication::main(juce::String&, juce::JUCEApplication*) + 415
26 com.cycling74.MaxMSP 0x0029eb7a
juce::JUCEApplication::main(int, char**, juce::JUCEApplication*) + 90
27 com.cycling74.MaxMSP 0x001c411c main + 76
28 com.cycling74.MaxMSP 0×00002972 _start + 216
29 com.cycling74.MaxMSP 0×00002899 start + 41

Thread 1 Crashed:
0 com.cycling74.MaxMSP 0x002d7d3f
juce::Component::setBounds(int, int, int, int) + 559
1 com.cycling74.MaxMSP 0x002b4046
juce::ListBox::updateContent() + 470
2 com.cycling74.MaxMSP 0×00103861
DataViewComponent::handleNotification(object*, symbol*, void*) + 1865
3 com.cycling74.MaxMSP 0x0012298e
jdataview_compnotify(DataViewComponent*, _jdv_notifier*) + 44
4 com.cycling74.MaxMSP 0x00054cca linklist_funall + 68
5 com.cycling74.MaxMSP 0x001228cc
jdataview_notifycomponents(_jdataview*, symbol*, void*) + 50
6 com.cycling74.MaxMSP 0x00123d47 jdataview_clear + 53
7 com.cycling74.MaxAPI 0x0283f127 jdataview_clear + 29
8 com.cycling74.pattrstorage 0x180bfa2a pattrwin_client_flat + 32
9 com.cycling74.pattrstorage 0x180bfb03 pattrwin_cwin_update + 39
10 com.cycling74.pattrstorage 0x180add81 pattrstorage_pattrwin_q
+ 29
11 com.cycling74.pattrstorage 0x180b97ac
pattrstorage_recall_gimme + 275
12 com.cycling74.pattrstorage 0x180b9902 pattrstorage_float + 60
13 com.cycling74.MaxMSP 0x0005baac outlet_float + 790
14 com.cycling74.MaxAPI 0x0281fd1a outlet_float + 54
15 com.cycling74.line 0x00eaea7f line_tick + 236
16 com.cycling74.MaxMSP 0×00025863 sched_takepoll + 495
17 com.cycling74.MaxMSP 0x000258fe sched_poll + 50
18 com.cycling74.MaxMSP 0x0005ec8e systimer_pollaction + 50
19 com.cycling74.MaxMSP 0x0005f0b6 mactimer_isr() + 100
20 …ple.CoreServices.CarbonCore 0x91aa7ecb TimerThread + 237
21 libSystem.B.dylib 0x959dd6f5 _pthread_start + 321
22 libSystem.B.dylib 0x959dd5b2 thread_start + 34

Thread 2:
0 libSystem.B.dylib 0x959ac506
semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x959de84f _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x959e00d3
pthread_cond_timedwait_relative_np + 47
3 …ple.CoreServices.CarbonCore 0x91a772fe
TSWaitOnConditionTimedRelative + 246
4 …ple.CoreServices.CarbonCore 0x91a770de TSWaitOnSemaphoreCommon
+ 422
5 …ple.CoreServices.CarbonCore 0x91aa8222 DeferredTaskThread + 70
6 libSystem.B.dylib 0x959dd6f5 _pthread_start + 321
7 libSystem.B.dylib 0x959dd5b2 thread_start + 34

Thread 3:
0 libSystem.B.dylib 0x959ac4a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x959b3c9c mach_msg + 72
2 com.apple.audio.midi.CoreMIDI 0x1649bf0f
XServerMachPort::ReceiveMessage(int&, void*, int&) + 101
3 com.apple.audio.midi.CoreMIDI 0x1648e477 MIDIInPortThread::Run()
+ 111
4 com.apple.audio.midi.CoreMIDI 0x1649207d
XThread::RunHelper(void*) + 17
5 com.apple.audio.midi.CoreMIDI 0x1649c9ee
CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x959dd6f5 _pthread_start + 321
7 libSystem.B.dylib 0x959dd5b2 thread_start + 34

Thread 4:
0 libSystem.B.dylib 0x959ac506
semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x959de84f _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x959e00d3
pthread_cond_timedwait_relative_np + 47
3 com.cycling74.MaxMSP 0×00290649
juce::WaitableEvent::wait(int) const + 105
4 com.cycling74.MaxMSP 0x003830ab juce::Thread::wait(int)
const + 27
5 com.cycling74.MaxMSP 0x002a43d8
juce::InternalTimerThread::run() + 216
6 com.cycling74.MaxMSP 0x003838b0
juce::Thread::threadEntryPoint(juce::Thread*) + 272
7 com.cycling74.MaxMSP 0×00290751
juce::threadEntryProc(void*) + 17
8 libSystem.B.dylib 0x959dd6f5 _pthread_start + 321
9 libSystem.B.dylib 0x959dd5b2 thread_start + 34

Thread 1 crashed with X86 Thread State (32-bit):
eax: 0x0000009c ebx: 0x002d7b21 ecx: 0×00000000 edx: 0×00000000
edi: 0x0000015e esi: 0×18208170 ebp: 0xb00a0a38 esp: 0xb00a09e0
ss: 0x0000001f efl: 0×00010246 eip: 0x002d7d3f cs: 0×00000017
ds: 0x0000001f es: 0x0000001f fs: 0x0000001f gs: 0×00000037
cr2: 0×00000000

/System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/
vecLib.framework/Versions/A/libBLAS.dylib
0x

_____________________________
Patrick Delges

Centre de Recherches et de Formation Musicales de Wallonie asbl

http://www.crfmw.be/max


June 23, 2008 | 9:53 am

Thanks, this is the window crash, and will be fixed in the upcoming 5.0.3 release.

Jeremy


June 23, 2008 | 10:17 am

Quote: Jeremy Bernstein wrote on Mon, 23 June 2008 11:21
—————————————————-
> If the crashing goes away when you close the client and storage windows, I suspect that the bug was fixed.
>
> jb
—————————————————-

Yep. It goes away when I close the client and storage windows. Thanks for looking into it so quickly.


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