Bug Report [Web] : jit.pwindow interp crash

Feb 15, 2007 at 2:04pm

Bug Report [Web] : jit.pwindow interp crash

userEmail ::
——————
lists@lowfrequency.org

bugHeader ::
——————
jit.pwindow interp crash

bugSummary ::
——————
jit.pwindow will instanstly crash max if there is a matrix directly connected to it with the “interp 1″ flag set

bugStepsReproduce ::
——————
1. See attached patch. Connect a matrix with an “interp 1″ attribute to a jit.pwindow with the “onscreen 0″ and “interp 0″ attributes

2. Set the jit.pwindow’s “interp” attribute to 1

3. Crash.

bugExpectedResults ::
——————
I expect the jit.pwindow to simply display the matrix.

bugActualResults ::
——————
Crash.

bugRegression ::
——————
When “onscreen 1″ is set on the pwindow, or “interp 0″ is set on the jit.matrix attached to it, crash does not occur.

bugNotes ::
——————
max v2;
#N vpatcher 497 313 1383 960;
#P window setfont “Sans Serif” 9.;
#P window linecount 1;
#P message 239 207 52 196617 interp $1;
#P toggle 241 180 15 0;
#P message 271 384 52 196617 interp $1;
#P toggle 273 357 15 0;
#P message 132 24 83 196617 read dishes.mov;
#P user jit.pwindow 43 474 162 122 1 0 0 0 1 0;
#P newex 44 276 224 196617 jit.matrix switcheroo 4 char 320 240 @interp 0;
#P message 140 68 28 196617 stop;
#P flonum 172 47 35 9 0 0 0 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P message 172 68 42 196617 rate $1;
#P message 109 68 28 196617 read;
#P flonum 78 47 35 9 0.5 0 1 3 0 0 0 221 221 221 222 222 222 0 0 0;
#P toggle 44 47 15 0;
#P newex 44 67 52 196617 metro 22;
#P newex 44 106 103 196617 jit.qt.movie 320 240;
#P window setfont “Sans Serif” 14.;
#P window linecount 4;
#P comment 253 44 263 196622 standard video color is a combination of 4 color “channels” – ALPHA , RED , GREEN & BLUE (in that order);
#P connect 3 0 2 0;
#P fasten 11 0 1 0 137 94 49 94;
#P fasten 8 0 1 0 145 94 49 94;
#P fasten 5 0 1 0 114 94 49 94;
#P fasten 6 0 1 0 177 94 49 94;
#P fasten 2 0 1 0 49 99 49 99;
#P connect 15 0 9 0;
#P connect 1 0 9 0;
#P connect 9 0 10 0;
#P connect 13 0 10 0;
#P connect 4 0 2 1;
#P connect 7 0 6 0;
#P connect 14 0 15 0;
#P connect 12 0 13 0;
#P pop;

#30301
Feb 15, 2007 at 3:30pm

#96531
Feb 15, 2007 at 4:24pm

#96532
Feb 15, 2007 at 5:34pm

On Feb 15, 2007, at 8:24 AM, evan.raskob [lists] wrote:

> Really?
>
> oops, forgot Max/Jitter version: Max 4.5.7, Jitter 1.5.3rc3
> OS X 10.4.8 ppc

Probably not going to be fixed in 1.5.3 (lowest of our development
priorities). I also can’t reproduce in 1.6.3b2.

I’ve never seen this reported before and the source code is
essentially the same for jit.pwindow in 1.5.3rc3 and 1.6.3b2, so make
sure you don’t have some old version of jit.pwindow or something in
your search path–i.e. try a fresh install and see if that still
crashes.

Otherwise you’ll need to take whatever logic into account to work
around this.

-Joshua

#96533
Feb 16, 2007 at 3:19pm

Ok, not a big priority at all, I was just creating an example patch.
I will check my jit.pwindow, but it’s not such a large problem that
I’d bother re-installing max over it.

-evan

On Feb 15, 2007, at 5:34 PM, Joshua Kit Clayton wrote:

>
> On Feb 15, 2007, at 8:24 AM, evan.raskob [lists] wrote:
>
>> Really?
>>
>> oops, forgot Max/Jitter version: Max 4.5.7, Jitter 1.5.3rc3
>> OS X 10.4.8 ppc
>
> Probably not going to be fixed in 1.5.3 (lowest of our development
> priorities). I also can’t reproduce in 1.6.3b2.
>
> I’ve never seen this reported before and the source code is
> essentially the same for jit.pwindow in 1.5.3rc3 and 1.6.3b2, so
> make sure you don’t have some old version of jit.pwindow or
> something in your search path–i.e. try a fresh install and see if
> that still crashes.
>
> Otherwise you’ll need to take whatever logic into account to work
> around this.
>
> -Joshua

#96534

You must be logged in to reply to this topic.