|
List Info
Thread: RE: Strange Memory Leak
|
|
| RE: Strange Memory Leak |
  United Kingdom |
2007-03-23 08:03:25 |
Does it make any difference if the global is called
something other than
test? (I know it's silly but...)
Danny
> -----Original Message-----
> From: dirgames-l-bounces nuttybar.drama.uga.edu
> [mailto:dirgames-l-bounces nuttybar.drama.uga.edu] On
Behalf Of Alexx
> Sent: 23 March 2007 12:58
> To: Director - Shockwave - and Flash Game Production
> Subject: Re: [dirGames-L] Strange Memory Leak
>
>
> > 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-L nuttybar.drama.uga.edu
> http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
>
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|
|
| Re: Strange Memory Leak |
  France |
2007-03-23 08:22:58 |
Danny Kodicek a écrit :
> Does it make any difference if the global is called
something other than
> test? (I know it's silly but...)
>
hehe, nice try, but no... in my main movie, the bug comes
from another
global variable
after a long search, I think I have found the scripts
causing this
problem, but I still don't understand why...
here is a simplified movie with the bug : http://www.alesk.fr
/leak_test.zip
run it and watch the memory inspector, the memory used by
program should
grow slowly
then, remove all the scripts from the dirjs castlib, close
director,
then reopen the movie -> no more bug
so, one of these scripts is the source of the problem, but I
don't see
wich one, since none of them is called from anywhere
maybe it's a simple thing... but I can't figure wich one :/
thanks for help
Alexx
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|
|
| Re: Strange Memory Leak |
  United States |
2007-03-23 08:41:57 |
At 2:22 PM +0100 3/23/07, Alexx wrote:
>here is a simplified movie with the bug : http://www.alesk.fr
/leak_test.zip
>
>run it and watch the memory inspector, the memory used
by program
>should grow slowly
The memory usage actually went down on the Mac. Is it a
Windows only issue?
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|
|
| Re: Strange Memory Leak |
  United Kingdom |
2007-03-23 09:08:35 |
----- Original Message -----
From: "Alexx" <earthwormjim free.fr>
> here is a simplified movie with the bug :
> http://www.alesk.fr
/leak_test.zip
>
> run it and watch the memory inspector, the memory used
by program should
> grow slowly
The problem appears to be due to you use of javascript,
which suggests its
not a memory leak but the standard issue of javascript
garbage collection.
>From some quick tests it appears once you've added some
javascript functions
to your moivie, a flag is set for the duration of the
Director authoring
instance that you've used javascript. This means regardless
of whether the
javascript functions are called you get the memory leak.
Further more that
even if you then create a new movie and just add the basic
frame script
sample you've given, the apparent memory leak will still
occur.
If however you close down Director, re-open it, paste just
the frame script
into a new movie and run that, memory usage is static. Same
as the result of
running you sample movie in D8.5
The worrying aspect though is when using javascript (even if
no functions
are called) lingo appears to be leaking memory, or rather
the automatic
garbage collection is not kicking in. I ran your test for
quite a while
(bumped framerate up to 999) and reached over 64 mb before
getting fed up.
Thats using 30 mb more than the default movie memory usage
and still no
automatic garbage collection. I even tried _System.gc() from
the message
window but that only freed up a few mb down to 54mb, so
still wasting a good
24 mb of memory.
Perhaps this is expected behaviour of javascript, i've never
used it, but
still something seams a little screwy here.
Noisecrime 2007
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|
|
| Re: Strange Memory Leak |
  Germany |
2007-03-23 09:52:51 |
Guys,
forget the memory inspector. This window isn´t accurate
anymore since a
long time, according to macr engineering.
--
Christophe Leske
___________________________________________
multimedial.de - info multimedial.de
Roseggerstr. 14
41564 Kaarst
Germany
0177 249 70 31
___________________________________________
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|
|
| Re: Strange Memory Leak |
  France |
2007-03-23 10:18:00 |
Hi,
>
> The worrying aspect though is when using javascript
(even if no
> functions are called) lingo appears to be leaking
memory, or rather
> the automatic garbage collection is not kicking in. I
ran your test
> for quite a while (bumped framerate up to 999) and
reached over 64 mb
> before getting fed up. Thats using 30 mb more than the
default movie
> memory usage and still no automatic garbage collection.
I even tried
> _System.gc() from the message window but that only
freed up a few mb
> down to 54mb, so still wasting a good 24 mb of memory.
>
> Perhaps this is expected behaviour of javascript, i've
never used it,
> but still something seams a little screwy here.
thanks for the test... and I think I've found how to prevent
the problem
: calling _System.gc() every frame fix the leak
it's a bit dirty, but working
bye
Alexx
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|
|
| Re: Strange Memory Leak |
  Sweden |
2007-03-23 10:24:23 |
Alexx skrev:
> Hi,
>>
>> The worrying aspect though is when using javascript
(even if no
>> functions are called) lingo appears to be leaking
memory, or rather
>> the automatic garbage collection is not kicking in.
I ran your test
>> for quite a while (bumped framerate up to 999) and
reached over 64 mb
>> before getting fed up. Thats using 30 mb more than
the default movie
>> memory usage and still no automatic garbage
collection. I even tried
>> _System.gc() from the message window but that only
freed up a few mb
>> down to 54mb, so still wasting a good 24 mb of
memory.
>>
>> Perhaps this is expected behaviour of javascript,
i've never used it,
>> but still something seams a little screwy here.
> thanks for the test... and I think I've found how to
prevent the
> problem : calling _System.gc() every frame fix the
leak
> it's a bit dirty, but working
>
> bye
>
> Alexx
> _______________________________________________
> dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
> http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
>
>
Cool. _system.gc() what does it do?? Garbage Collect ??
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|
|
| Re: Strange Memory Leak |
  United States |
2007-03-23 10:26:52 |
It would be VERY NICE if you actually mentioned the platform
this
occurred for you on.
I have no memory issues with this on the mac.
On Mar 23, 2007, at 8:22 AM, Alexx wrote:
> Danny Kodicek a écrit :
>> Does it make any difference if the global is
called something
>> other than
>> test? (I know it's silly but...)
>>
> hehe, nice try, but no... in my main movie, the bug
comes from
> another global variable
> after a long search, I think I have found the scripts
causing this
> problem, but I still don't understand why...
>
> here is a simplified movie with the bug : http://www.alesk.fr/
> leak_test.zip
>
> run it and watch the memory inspector, the memory used
by program
> should grow slowly
>
> then, remove all the scripts from the dirjs castlib,
close
> director, then reopen the movie -> no more bug
> so, one of these scripts is the source of the problem,
but I don't
> see wich one, since none of them is called from
anywhere
>
> maybe it's a simple thing... but I can't figure wich
one :/
>
> thanks for help
>
> Alexx
>
> _______________________________________________
> dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
> http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|
|
| Re: Strange Memory Leak |
  France |
2007-03-23 10:37:17 |
Alex Zavatone a écrit :
> It would be VERY NICE if you actually mentioned the
platform this
> occurred for you on.
> I have no memory issues with this on the mac.
sorry : Win XP Pro , Director 10.1.1
bye
Alexx
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|
|
| Re: Strange Memory Leak |
  Sweden |
2007-03-23 10:47:37 |
I don't know if this apply to director, but .Net has garbage
collection
aswell, and calling that every "frame" is not a
good idéa
performance-vise. If you _have_ to call the garbage
collector, I'd do
with a longer interval say, every 10 sec?
My 2 cents
/Christoffer
Alexx skrev:
> Hi,
>>
>> The worrying aspect though is when using javascript
(even if no
>> functions are called) lingo appears to be leaking
memory, or rather
>> the automatic garbage collection is not kicking in.
I ran your test
>> for quite a while (bumped framerate up to 999) and
reached over 64 mb
>> before getting fed up. Thats using 30 mb more than
the default movie
>> memory usage and still no automatic garbage
collection. I even tried
>> _System.gc() from the message window but that only
freed up a few mb
>> down to 54mb, so still wasting a good 24 mb of
memory.
>>
>> Perhaps this is expected behaviour of javascript,
i've never used it,
>> but still something seams a little screwy here.
> thanks for the test... and I think I've found how to
prevent the
> problem : calling _System.gc() every frame fix the
leak
> it's a bit dirty, but working
>
> bye
>
> Alexx
> _______________________________________________
> dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
> http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
>
_______________________________________________
dirGames-L mailing list - dirGames-L nuttybar.drama.uga.edu
http://nuttybar.drama.uga.edu/mailman/listinfo/dirgames
-l
|
|
|
|