Forums > MaxMSP

Help with constant crashes, please..

April 4, 2014 | 11:58 am

This Max patch, i’m working on, crashes constantly, doesn’t matter if its in use or not.

I really can`t find the way to make it work.

I’m on a MacBook Pro
2,2 GHz Intel Core i7
8 GB Ram

Mac OS 10.7.1
Max 6.1.7 i have reinstalled and still the same…….Help please !!!

  • This topic was modified 6 months by  lesespejo.

April 4, 2014 | 12:21 pm

It’s not crashing here, but I do get dozens of "OSC-route: No such object" messages in the Max window. Perhaps it’s related to something in that patcher.


April 4, 2014 | 12:21 pm

It’s not crashing here, but I do get dozens of "OSC-route: No such object" messages in the Max window. Perhaps it’s related to something in that patcher.


April 4, 2014 | 12:53 pm

Sorry, sure that’s because you don’t have the OSC-route object (CNMAT) installed in your externals folder.

This is a patch controlled with Lemur app for iPad, and i’m using OSC and many OSC-route objects.


April 4, 2014 | 1:01 pm

I know. I was just wondering if the crash might be related to the inclusion of those objects in your patcher.


April 5, 2014 | 3:14 am

Ok. I have substituted all the OSC-route objects (hundreds of them) for the route object, to discard an external’s problem, but the crash repeats, i think it was the only third party object i was using.

Help please !!!!

here is the new version.


April 5, 2014 | 5:08 am

Have a look in the task manager. The reason the patch is crashing is the memory usage is continually increasing until it reaches 2GB which is the Max 32 bit limit. I don’t have time to identify the exact problem but it’s possible you may have some form of infinite loop. I’d suggest checking all the processes that happen when the patch loads. To help keep track of these issues it may be helpful to have a single initialisation subpatcher triggered by a single loadbang rather than loadbangs spread throughout various subpatchers.

The reason it may not be crashing for others is because they may have run it in 64 bit and it would therefore take longer to reach the memory limit and they may have exited the patch before the crash.

  • This reply was modified 6 months by  tomprescott1989. Reason: 64 bit clarification

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