Forums > MaxMSP

Crash — any ideas?


jbm
January 31, 2006 | 12:35 pm

I’ve had a couple of crashes recently.
Here’s a crash report, if anyone has any ideas.
It looks like something’s bugging out with seq~,
but I’ve no idea whether this is me or the object.
I haven’t changed anything recently, but I also don’t
know whether any real changes were made to seq~ in
4.5.6(?).

G5 dual 1.8, OS X.4.4,
1.5 GB RAM, MaxMSP 4.5.6

Thread 24 Crashed:
0 seq~ 0x185fb900 seq_between + 152
1 seq~ 0x185fbb24 seq_perform + 328
2 MaxAudioLib 0x007cdd7c dspchain_tick + 80
3 MaxAudioLib 0x007cbf1c ad_process + 392
4 CoreAudio=! 0x15196b34 coreaudio_onedevice_ioproc + 276
5 com.apple.audio.CoreAudio 0x91414ac8 IOA_Device::CallIOProcs(AudioTimeStamp const&, AudioTimeStamp const&, AudioTimeStamp const&) + 376
6 com.apple.audio.CoreAudio 0x914147dc HP_IOThread::PerformIO(AudioTimeStamp const&) + 532
7 com.apple.audio.CoreAudio 0x914127ec HP_IOThread::WorkLoop() + 1156
8 com.apple.audio.CoreAudio 0×91412354 HP_IOThread::ThreadEntry(HP_IOThread*) + 16
9 com.apple.audio.CoreAudio 0x914031d4 CAPThread::Entry(CAPThread*) + 96
10 libSystem.B.dylib 0x9002b200 _pthread_body + 96

Thread 24 crashed with PPC Thread State 64:
srr0: 0x00000000185fb900 srr1: 0x100000000200f030 vrsave: 0×0000000000000000
cr: 0×44000274 xer: 0×0000000000000000 lr: 0x00000000185fbb24 ctr: 0x0000000090048a80
r0: 0×0000000000000000 r1: 0x00000000f0101880 r2: 0x0000000001a57200 r3: 0x00000000343b7a60
r4: 0x00000000746f2061 r5: 0×0000000000000000 r6: 0x000000001783e228 r7: 0xffffffffffffffff
r8: 0×0000000000000001 r9: 0×0000000000000001 r10: 0x00000000180a1fc0 r11: 0×0000000000000000
r12: 0x00000000a0007598 r13: 0×0000000000000000 r14: 0×0000000000000000 r15: 0×0000000000000000
r16: 0×0000000000000000 r17: 0×0000000000000000 r18: 0×0000000000000000 r19: 0x00000000357f69c8
r20: 0×0000000000000000 r21: 0x000000000184d7f8 r22: 0×0000000000000100 r23: 0×0000000001878044
r24: 0×0000000000000000 r25: 0x00000000015c6ae8 r26: 0×0000000000000200 r27: 0×0000000000000040
r28: 0x0000000001b57c00 r29: 0x0000000001b6d9c4 r30: 0x00000000343b7a60 r31: 0×0000000000000040

thanks,

J.


January 31, 2006 | 6:51 pm

Your guess is as good as mine unless you provide us with a bit more
information. While we appreciate the crash report, it is only a small
piece of the story. Please send a simple example patch with numbered
steps to reproduce the crash.

Cheers,
Andrew B.



jbm
February 1, 2006 | 9:19 am

yeah, I kind of figured you’d need more…
unfortunately, I can’t really reproduce the problem
in a simple or small way. I’ll keep poking away at
it. Were there any major changes to seq~ in 4.5.6,
btw?

J.


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