Max crashes / How to read an Apple Report (console)


    Jan 17 2021 | 1:43 pm
    Hello everyone,
    I'm using a Max patch for my new AV performance p(O)st : http://www.alexaugier.com/post/
    Recently, I have Max crashes. Its' a very stressful situation because I have some gigs in a few weeks ! The crashes can appear at any moments: sometime after 10 minutes, sometime after 1 hour... Unfortunately, I don't know what gesture or manipulation create this crash.
    The Max patch is too complex to explain. What I need : understand the Apple report that I had after the crash to understand what and where is the problem. I don't have any error in the Max console (it's very clean). I add, in CC, the 2 last reports.
    My configuration : iMac 3,5 GHz Intel Core i7 (27 inch, end 2013) or MacBook Pro (15 inch, 2019) for my live performance (I have the same problem with the laptop).
    In both computers : OS 10.14.6 Max 8.1.5 Processing 3.5.3 Madmapper 3.7.2
    Thank you a lot !

    • Jan 17 2021 | 3:22 pm
      So, the crash report states that Max is generating a EXC_BAD_ACCESS (SIGSEGV) exception, which means the program is trying to access a place in memory no longer available, most likely caused by a bug (so it's not your patch's fault). Is there any particular reason you're not using the last version of Max (8.1.8)? If I were you, I'd try and update Max and see if hopefully the bug has already been fixed, and if not contact support and send them your patch so they can hopefully reproduce the bug and fix it.
    • Jan 17 2021 | 4:43 pm
      Hello,
      Thank you a lot for your reply. Happy to know that the Max patch is right.
      I've recently updated Max for the last version (8.1.8) but, unfortunately, it doesn't work fine. I have more problems !!! That's why I prefer using time to understand the problem with this version 8.1.5. I did this patch a long time now (all gigs cancelled because of covid-19 last year) and it's a little bit complicated to understand again everything I made.
      Is there a solution as ligher max patch ?
      Thank you again
    • Jan 17 2021 | 5:07 pm
      Just one more question : is it only a bug or is it a hardware limit (not enough memory) that allows me to add more memory ?
      thank you