elevatormusicmaker

I'm using Max 7. I have a rather complex patch that crashes every time I bang a particular message, and I get the error message, ""print: Too many lines (more than 10000) were posted to the Max Window at once; output truncated" in that yellow area above and Max freezes indefinitely, forcing me to Force Quit and relaunch. Then I have to try and find the problem again without actually initiating the process that causes the problem, otherwise Max will freeze again :(

I wouldn't expect anyone to go looking for the actual problem in the patch (because its a mess). I'm am just curious why Max crashes, thats all, instead of disabling the outputs (which is the usual behavior from Max that I am more familiar with). It seems impossible to find the issue because of this.

locating-a-problem-that-causes-max-7-to-crash

1) If you are not on Max 7.0.3 try updating. (Any other version of Max can be compressed and used later if 7.0.3 causes issues.) There were some issues with sending large streams of data to the Max console in earlier versions of Max 7.

2) remove all print objects and see if there is still an issue.

The debugging-generative-error.maxpat has a lot of print objects, and sending a lot of data very quickly to the Max Console can cause issues like application hang.

If there are still errors after removing the print objects post back here.

1) If you are not on Max 7.0.3 try updating. (Any other version of Max can be compressed and used later if 7.0.3 causes issues.) There were some issues with sending large streams of data to the Max console in earlier versions of Max 7.
2) remove all print objects and see if there is still an issue.
The debugging-generative-error.maxpat has a lot of print objects, and sending a lot of data very quickly to the Max Console can cause issues like application hang.
If there are still errors after removing the print objects post back here.


Locating a problem that causes Max 7 to crash