[BUG] cycle~ to rect~ sync makes max crash 5.1.7 os x 10.5.8


    Mar 04 2011 | 9:20 am
    isolated to just 2 objects. steps to reproduce:
    1. turn on audio processing in dsp status
    2. make a [rect~ 50]
    3. make a [cycle~ 201]
    4. connect cycle's output to rect's "sync input" on the right
    machine running max msp jitter m4l 5.1.7 on os x 10.5.8 macbook 2.4ghz core 2 duo
    tried on a mbp running 10.6.4 and it does not crash.
    not complaining or anything but i accidently made this connection right in the middle of a slightly arrogant "look how cool max is" demo. lost the patch and nerds laughed at me.

    • Mar 04 2011 | 9:22 am
      Thread 7 Crashed:
      0 com.cycling74.rect~ 0x188c7c5f rect_perform + 1227
      1 com.cycling74.MaxAudioAPI 0x15d6989c dspchain_tick + 90
      2 com.cycling74.MaxAudioAPI 0x15d682cc ad_process + 470
      3 com.cycling74.ad_coreaudio 0x187365c3 coreaudio_twodevice_ioproc + 537
      4 com.apple.audio.CoreAudio 0x95bc0177 HP_IOProc::Call(AudioTimeStamp const&, AudioTimeStamp const&, AudioBufferList const*, AudioTimeStamp const&, AudioBufferList*) + 319
      5 com.apple.audio.CoreAudio 0x95bbfe68 IOA_Device::CallIOProcs(AudioTimeStamp const&, AudioTimeStamp const&, AudioTimeStamp const&) + 274
      6 com.apple.audio.CoreAudio 0x95bbfd44 HP_IOThread::PerformIO(AudioTimeStamp const&) + 1246
      7 com.apple.audio.CoreAudio 0x95bbe11f HP_IOThread::WorkLoop() + 1239
      8 com.apple.audio.CoreAudio 0x95bbdc43 HP_IOThread::ThreadEntry(HP_IOThread*) + 17
      9 com.apple.audio.CoreAudio 0x95bae480 CAPThread::Entry(CAPThread*) + 96
      10 libSystem.B.dylib 0x91dbf155 _pthread_start + 321
      11 libSystem.B.dylib 0x91dbf012 thread_start + 34
    • Mar 04 2011 | 9:30 am
      Max crashed after ±30s on my iMac under X.6.6., same crashlog.
      p
    • Mar 04 2011 | 1:53 pm
      Same here. Max 5.1.8, macbook pro core 2 duo 2.8 ghz, os x 10.6.6
      m
    • Mar 04 2011 | 4:43 pm
      Thanks - I can reproduce. Looks like it is Mac only.
      -A
    • Mar 04 2011 | 7:13 pm
      This is fixed for the 5.1.8 release
      Thanks
      -A
    • Mar 04 2011 | 7:37 pm
      fantastic!