sticky max crashes / midiin bug

Thijs Koerselman's icon

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

cebec's icon

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.

Thijs Koerselman's icon

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

T_

Thijs Koerselman's icon

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_