[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Gnash-dev] Memory use

From: strk
Subject: [Gnash-dev] Memory use
Date: Mon, 14 Dec 2009 23:34:55 +0100

Hi all,
as some of you may have been noticing I've spent some time 
on analyzing high memory use of Gnash during execution of potlatch.
Full story here:

The problem is many AS objects are allocated in a loop
(around 3500 iterations) and are only destroyed at the
very end of actions execution.

The amount of memory allocated by the end of action execution
is over 1Gb. The GC run properly drops most of these objects
(altought memory isn't released to the system, despite GLIBCXX_FORCE_NEW).

Now, beside the release of resources to the system, which at this point
is secondary, what's interesting is that running the GC earlier can
keep the memory much much lower.
For example, with the testcase attached to the bug we can from
723mb to 260mb.

The problem is that running the GC is very expensive as we need
to scan all reachable objects.

Currently the only heuristic to avoid GC runs is based on the number
of collectable resources allocated since last run, which defaults to 50
and can be changed by exporting the GNASH_GC_TRIGGER_THRESHOLD environment

Can anyone think of other strategies to decide *when* to run the GC ?


 Free GIS & Flash consultant/developer      ()  ASCII Ribbon Campaign  /\  Keep it simple! 

reply via email to

[Prev in Thread] Current Thread [Next in Thread]