On 4/12/09 07:51, Wolf Drechsel wrote:
Interesting to watch is that according to "top" inkscape-bin grabs 90% of CPU power and stays on that for many minutes (tried it for nearly 40 minutes).
I'm clueless at the moment. What you could try to get more data while inkscape-bin is running:
- open 'Activity Monitor' (graphical 'top')
- select 'inkscape-bin'
- 'View > Inspect Process', select 'Open Files and Ports' look at the list for any suspicious files inkscape-bin loads from outside the application bundle
Assuming you mean "Prozeß-Information" in the German version, I paste it here - as I will not be able to make any sense from that:
<snip>
looks ok as far as I can tell. Loads the same libs from the bundle, and a lot more from '/System/Library/{CoreServices|Frameworks}' then 0.47 on Leopard, but this could be due to the differences between Tiger and Leopard?
- 'View > Sample Process', save the result as text file and attach it, maybe it helps to determine where inkscape-bin hangs
"Prozeß-Analyse" in German? - Is attached as a file.
compare yours to the attached process samples of http://thread.gmane.org/gmane.os.apple.macports.devel/10079 and http://trac.macports.org/ticket/21679, which is a duplicate of http://trac.macports.org/ticket/21624
Which version of pango do you have installed? If it's 1.26.0, try this fix:
| Deactivated pango 1.26.0, reactivated pango 1.24.5, rebuilt all of | pango's direct dependents and then inkscape
~suv