Forums > MaxMSP

STACK OVERFLOW… HELP

April 10, 2009 | 10:10 pm

I have gone to open one of my project, and it will not open. A message comes up saying "stack overflow" "objects are probably connected in a loop. Choose resume to restart the scheduler". Yet the program crashes. I do have an older copy of the file, but I will have lost about 20hours work, which I really need to get back… is there anything I can do????????????



baz
April 10, 2009 | 10:36 pm

Can’t you find the problem without restarting the scheduler?

If you can’t even open it without Max crashing you should be able to make some sense of it as text (Open As Text). If it is crashing on open (without touching anything), my guess is the feedback starts with loadbang or loadmess, so you want to delete something like:

{
"box" : {
"maxclass" : "newobj",
"text" : "loadbang",
"numinlets" : 1,
"fontsize" : 12.0,
"numoutlets" : 1,
"outlettype" : [ "bang" ],
"id" : "obj-1",
"patching_rect" : [ 180.0, 157.0, 60.0, 20.0 ],
"fontname" : "Arial"
}

}

Another really cool way to crash Max is to have the name of a patcher inside itself.


April 10, 2009 | 10:38 pm

If you’ve got loadbangs in your patch there’s a way to suppress them when a patch is opened. Hold down shift and command (ctrl) keys while loading.

If that doesn’t work try opening as text in a text edit program, copy the text and paste into an empty patcher window.
T


April 10, 2009 | 11:16 pm
baz wrote on Fri, 10 April 2009 16:36
Another really cool way to crash Max is to have the name of a patcher inside itself.

i think you mean, "instantiate the patcher as an object within itself" which would obviously cause the patcher to recursively look for itself before its ‘self’ has been defined fully(not just the ‘name’ of a patcher, right? technically, you could use the ‘name’ no problem in a

type object…).


April 11, 2009 | 1:06 am
RabidRaja wrote on Fri, 10 April 2009 18:16
baz wrote on Fri, 10 April 2009 16:36
Another really cool way to crash Max is to have the name of a patcher inside itself.

i think you mean, "instantiate the patcher as an object within itself" which would obviously cause the patcher to recursively look for itself before its ‘self’ has been defined fully(not just the ‘name’ of a patcher, right? technically, you could use the ‘name’ no problem in a

type object…).

Just tried it as I was curious. Made a patch, saved it, then added the object with its name into it. No problem, showed up fine, can double-click to open. But upon saving, the Max window gave an error:

"perhaps you have mistakenly named a patcher file the same name as an object it contains. this is not permitted."

But it didn’t crash here, on XP, 5.0.6.

A subpatch with the same name is fine, since it’s part of the main patch and is unique, but putting the main patch into it would also cause the error.

This is kind of hurting my brain…



baz
April 11, 2009 | 4:29 am

Yeah, this makes Max 4.6 crash. Interesting.
I call a patch pants.maxpat and instantiate pants in pants.maxpat. Fine. If I save pants.maxpat (creating the hall-of-mirrors), Max4 crashes.
In Max5, the newly instantiated pants is fine on saving pants.maxpat, but the pants pants contains is "No such object". Also, it doesn’t seem like the pants in pants.maxpat is sending out signal. Someone must have decided to disallow these kinds of shinanegins.
But yes, no crash.


April 11, 2009 | 11:26 am

"If you’ve got loadbangs in your patch there’s a way to suppress them when a patch is opened. Hold down shift and command (ctrl) keys while loading."

This let me open my project! Thanks Terry… AND Thanks 2 every one for there input. Really saved me a lot of time.


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