> > On the subject of which, you could also try
> >
> > global test
> >
> > on enterframe me
> > test = 0
> > test = vector(0,0,0)
> > end
> >
> > It might be the continual setting to the *same*
vector that's
> > confusing the garbage collector - it looks, sees
that the
> vector is the same, ignores it.
> > Or something like that...
> >
> nope that's not it... If I run this test from a fresh
> director session, no problem occurs, the ram counter is
> static the problem comes from the movie I'm working on,
when
> running it, it seems to break something in director,
and then
> the leak occurs.
>
> I really don't understand why... I have removed all the
> initialization stuff from the startmovie handler, and
put
> only my test frame script at frame 1 and the bug is
still
> here then it could be a bug in the dir file itself ??
>
> I'm cursed :(
Have you maybe got a movieScript with an on vector handler
by mistake? Or
maybe an on new() handler that's somehow being called?
Danny
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|