RE: Strange Memory Leak

 > Well, had you tried to create the vector entity 1
frame back? 
> and in case you need to put it in 0
> 
> on enterframe me
> test.x = 0
> test.y = 0
> test.z = 0
> end
> 
> Maybe the garbage collector drives nuts if you create
an 
> instance of the vector several times in one second.

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...

Danny

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

> 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 :(

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

ive tested it and ive got the same result.

nb

Alexx skrev:
>
>> 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 :(
>
> _______________________________________________
> 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