Forums > MaxMSP

sticky max crashes / midiin bug

Feb 10 2006 | 3:58 pm

All of the crashes I was having lately, using 4.5.6 have been causing max to
stick in my taskmanager for at least 5 minutes. After a while I noticed that
this was happening in almost every case with different bugs and patches. I
started crashing my patch on purpose while stripping it down to the objects
that cause the stickyness.

It finally came down to [midiin]. Which makes sense since I almost always
have a path / subpatch with the object loaded.

steps to reproduce:

– make a patcher with [midiin]
– bang the following js to crash max:

function bang(){
x = this.patcher.newobject("toggle",122,90,15,0);


windows xp sp2 / max 4.5.6

ps: Is this a javascript bug too? You shouldn’t delete a non-existing
object, but just an error message would be nice. Now that I know how
dangerous the remove function is I use an if-statement to be sure. From my
own experience I know that it’s really easy for someone learning js to
crash max like this. At least I used to;-)

Feb 10 2006 | 4:46 pm

It crashes Max on my Dell Optiplex GX280 (work) system with stock hardware but max.exe is not sticking. i’ll try on my other system.

Feb 10 2006 | 7:39 pm

to be sure I just did a fresh restart and turned of my firewire soundcard,
but it’s still there. (dell inspiron 9300).


Feb 13 2006 | 5:31 pm

Can anyone please confirm this bug / behavior on windows xp sp2? I’m
sure midiin is at least one of the objects causing this on my system.


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

Forums > MaxMSP