List Info

Thread: RE: Strange Memory Leak




RE: Strange Memory Leak
country flaguser name
United Kingdom
2007-03-23 07:45:15
 > > 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-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

Re: Strange Memory Leak
country flaguser name
France
2007-03-23 07:58:13
> Have you maybe got a movieScript with an on vector
handler by mistake? Or
> maybe an on new() handler that's somehow being called?
>   
none of these :(
the problem is the same if I use test=image(32,32,32)
instead of 
vector(0,0,0)
also tested with a string or an integer : same bug !

_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

Re: Strange Memory Leak
country flaguser name
Germany
2007-03-23 08:12:10
did you try to set it void before re setting it ?



>> Have you maybe got a movieScript with an on vector
handler by mistake? Or
>> maybe an on new() handler that's somehow being
called?
>>   
> 
> none of these :(
> the problem is the same if I use test=image(32,32,32)
instead of 
> vector(0,0,0)
> also tested with a string or an integer : same bug !
> 
> _______________________________________________
> dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
> http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
> 
> 

_______________________________________________
dirGames-L mailing list  -  dirGames-Lnuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l

[1-3]

about | contact  Other archives ( Real Estate discussion Medical topics )