sticky max crashes / midiin bug

Feb 10, 2006 at 3:58pm

sticky max crashes / midiin bug

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);
this.patcher.remove(x);
this.patcher.remove(x[0]);
}

T_

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;-)

#24367
Feb 10, 2006 at 4:46pm

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.

#70382
Feb 10, 2006 at 7:39pm

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

T_

#70383
Feb 13, 2006 at 5:31pm

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.

T_

#70384

You must be logged in to reply to this topic.