Best way to debug Max for Live Crashes

I have crashed Max for Live more than I have ever crashed any other program in all of my 20 years working with computers.

I am not complaining because I am working on something I like a lot. I like to think is cutting edge and cool and I am assuming that is the problem. I do however really want to solve the problem.

Most of the time when I close my Max for Live patch either Max or Live crashes.

My question is...

a) What is the best way to debug my patch. Everything is good until I close the patch and at that point the log is no longer available (I think)? Is it in the Live crash report and if so how in the heck do I use that? Is there another log I can utilize?

b) Is this a question for Ableton or Cycling 74?

Thanks for your help.

 

 

9 followers

subcycle 2 years ago | 0 comments

1 answer

  • TheAnt
    contribution
    14 answers
    32 votes received
    1 vote

    Hi,

    I use M4L and I do not have this happen to me. I have an i7 PC with Windows 7 64bit.

    You don't mention if you have a mac or a PC but either way I think I would deal with the boring stuff first. I think it would be a good idea to unistall completely Ableton and M4L, restart and reinstall using the latest versions. If you are on a PC I would delete the program folders for both after the restart (beofre the reinstall).

    If you are still having the same problem I would try and see if there is any patern to the crash. I am thinking maybe there is a particular object that is causing this issue. Maybe create test patches slowly removing objects, or adding, to see if you can see if an object is causing this issue.

     

    Then, armed with this info, I think I would go to the Cycling '74 M4L forum:

    http://cycling74.com/forums/forum.php?id=10

    2 years ago | 0 comments

You need to be logged in, have a Live license, and have a username set in your account to be able to answer questions.

Answers is a new product and we'd like to hear your wishes, problems or ideas.