Another thing is that current CVS supports use of an environment variable to specify how many new GC-managed objects should be allocated before a new collection cycle starts. Try exporting GNASH_GC_TRIGGER_THRESHOLD=1
--strk; On Tue, Apr 29, 2008 at 08:38:18AM +0200, strk wrote: > On Tue, Apr 29, 2008 at 11:51:47AM +0800, Hong Yu wrote: > > > > We have ported Gnash0.8.2 to ARMv6 platform. However Gnash0.8.2 fails to > > play one of our .swf file satisfactorily, by ending with > > 'std::bad_alloc' message, indicating that it consumes out 120MB and more > > memory. Therefore we wish to improve Gnash0.8.2's performance for ARM. > > Would anyone have suggestions and/or clues on how we can gradually > > achieve the goal of improving Gnash for low level platform(s)? Thanks. > > My suggestion is to find out what's taking up all the memory as first > thing. One of valgrind tools should help (massif). > > valgrind --tool=massif gtk-gui <movie> > > --strk; _______________________________________________ Gnash-dev mailing list [email protected] http://lists.gnu.org/mailman/listinfo/gnash-dev
