[Top][All Lists]

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

Re: [Gnash-dev] Memory use

From: Rob Savoye
Subject: Re: [Gnash-dev] Memory use
Date: Mon, 14 Dec 2009 15:48:53 -0700
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20090922 Fedora/3.0-3.9.b4.fc12 Lightning/1.0pre Thunderbird/3.0b4

On 12/14/09 15:34, strk wrote:

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

Back when I worked on LISP systems (25 years ago), the GC would run in a separate thread based on a timer, as opposed to any other action. Each object was tagged as to it's state, and the GC would just remove anything with the appropriate state. Some customers of mine back then would often play games with the time slice for the GC to get the optimal memory uses. (back then memory was still expensive)

This might not help in this case, unless the objects are tagged as unused before the action is complete. I'm not exactly suggesting we do it this way, I haven't really thought through how it would work in Gnash, but you did ask for other ideas... :-)

Just as a note, there is some other memory profiling built into Gnash that uses mallinfo() to get memory stats from the kernel. There are also some utility functions in gmemory.h like startCheckpoint(), endCheckpoint(), to get finer grained info of where memory was going. I also added support to jemalloc to support mallinfo() as well.

Out of curiosity, did you run your tests with or without jemalloc ? It's better tweaked for all the small allocations of memory that an OOPS language uses.

        - rob -

reply via email to

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