gnash-dev
[Top][All Lists]
Advanced

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

Re[2]: [Gnash-dev] Re:Serious performance problem


From: Udo Giacomozzi
Subject: Re[2]: [Gnash-dev] Re:Serious performance problem
Date: Wed, 2 May 2007 15:49:28 +0200

Hello Sandro,

Wednesday, April 25, 2007, 5:41:25 PM, you wrote:
>> Yes, but applies only to execute_frame_tags() which is not the problem
>> in this case. The call to do_actions() is still done.

SS> do_actions executes queued actions removing them from the queue.
SS> execute_frame_tags() is what queues the actions, so do_actions
SS> does nothing if execute_frame_tags()
SS> is not called.

Okay, then the actions come from somewhere else (still queued?).


>> ... -> do_actions() -> execute_actions() -> execute_action() -> ... -> 
>> set_invalidated()

SS> Could it be a memory corruption due to the
SS> character::get_text_value returning
SS> the adress of a local variable ?

Can't check right now because Gnash won't build. However, I noticed
the same behaviour already a few weeks ago.


>> A few days ago I noticed that static characters get removed and placed
>> again on a display list when a sprite loops back to it's first frame.
>> 

SS> This should be only true for multi-framed sprites.
SS> Anyway, if a *child* is removed and placed again of course it's
SS> first frame actions are executed again.

This is what I *believe* is happening.

Udo





reply via email to

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