Bugs item #2652974, was opened at 2009-03-01 23:04
Message generated for change (Comment added) made by gballintijn
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=757416&aid=2652974&group_id=144022

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Usability
Group: SVN version
Status: Open
Resolution: None
Priority: 7
Private: No
Submitted By: Genete (genete)
Assigned to: Nobody/Anonymous (nobody)
Summary: Canvas is not refreshed

Initial Comment:
Scrubbing the timeline, pressing the JMP action or the redraw button seems to 
be ignored by the main window renderer. For very simple files it says 
"Rendering..." long time in the status bar and the window doesn't refresh. It 
happens since svn 2340
I've returned to svn 2305 and it doesn't appear. Scrubbing the timeline works 
fine. Zelgadis reported in IRC that 2316 works fine as well.
I guess that it comes from changes 2320 and 2321.

----------------------------------------------------------------------

>Comment By: Gerco Ballintijn (gballintijn)
Date: 2009-03-03 00:38

Message:
I also noticed this problem. I noticed two things when the canvas refresh
was stalled with the "Rendering..." message. The first thing I noticed was
that in my case it was every other refresh that stalled (all odd ones). The
second thing is that both synfigstudio and my X server were using the CPU,
but not completely (40% in total). The third is that I also noticed that
using only one "core" did not prevent the problem. However, using one
"core" did appear to reduce the frequency of the refresh problem. Then I
ran synfigstudio in GDB to monitor its execution. First, GDB indicates that
a new thread is created and destroyed continously. This might be what
Genete also sees. Unfortunately, when I suspended execution of synfigstudio
only a few entries on the stacktrace resolved to symbolic names so its
unclear what's going on. I think the symbolic names were part of the Glib.
I'm not sure if the tile renderer itself is the problem. If I understand
correctly the tile renderer divides up the work and fills a work queue,
used by potentially multiple threads that renderer each individual tile. I
think the problem can also occure during and after this queueing.

----------------------------------------------------------------------

Comment By: Genete (genete)
Date: 2009-03-01 23:52

Message:
I've noticed that taskset doesn't affect the problem. It still appearing.
When I export SYNFIG_DISABLE_TILE_RENDER=1 then the endless "Rendering..."
message doesn't happen. It always end rendering the frame. So I guess it is
something related to the tile render. :-/

----------------------------------------------------------------------

Comment By: Genete (genete)
Date: 2009-03-01 23:33

Message:
I realized that the problem still happening.
I'll see if assigning synfigstudio to only one core fix the problem.
The fact is that the navigator panel is rendered properly and respond to
all the mouse clicks but the main window keeps saying: "Rendering...". I've
leave it running (not move the timeline) and watch the process in the task
manager. Temporarily a synfigstudio binary executable appeared under as
"zombie" in the task list. 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=757416&aid=2652974&group_id=144022

------------------------------------------------------------------------------
Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA
-OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise
-Strategies to boost innovation and cut costs with open source participation
-Receive a $600 discount off the registration fee with the source code: SFAD
http://p.sf.net/sfu/XcvMzF8H
_______________________________________________
Synfig-devl mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/synfig-devl

Reply via email to