pango based apps have signifigant performance loss

[distributed@…]

I had the same symptoms as the original poster in #21220, even though on Tiger, without upgrading anything.

I wasn't sure if I screwed up my port installation, so I followed the FAQ entry to uninstall MacPorts, then installed the newest version of XCode for Tiger and XQuartz 2.4.0 (xorg-server 1.5.3-apple14), then MacPorts (1.8.1) again. In MacPorts I installed first gv, then viking and then wireshark. The symptoms still are the same.

[blb@…]

Can you attach the output you get when trying to run wireshark?

[distributed@…]

Sure. It is only one line:

shaman:~ joe$ wireshark
Xlib:  extension "RANDR" missing on display "/tmp/launch-nl9G7s/:0".

[shubnub@…]

I see similar behavior, but if I wait long enough, the CPU spikes and, eventually, the Wireshark splash screen comes up with the "Registering dissector..." progress bar. Unfortunately, progress is _extremely_ slow. I waited an hour and only got -- IIRC -- about 33% of the way through before killing it. This is on a MBP3,1 running 10.6.1 w/4GB of RAM.

[distributed@…]

Hehe, I didn't wait that long, but you're right, after about 1 minute the splash screen turns up. But as in your case it is dog slow. (MBP4,1)

[blb@…]

For anyone who's seeing it run slowly, what version of pango is installed and active? Use:

$ port installed pango

If it's 1.26.0, it could be pango's fault (see #21624 and #21678 for examples).

[distributed@…]

Bingo. My version of pango is 1.26.0. I now installed pango 1.24.5 (as described in ​http://iparrizar.mnstate.edu/~juan/urania/2008/12/05/fixing-libxml2-problems-with-macports/), rebuilt first gtk2 and then wireshark. It now works like a charm.

Thank you for your help!

[shubnub+macports@…]

Hey, how about that? Pango 1.24.5 solves the problem. I followed the directions at #21678 and rebuild wireshark, now it's all speedy fast.

[jeremyhu (Jeremy Huddleston Sequoia)]

​http://bugzilla.gnome.org/show_bug.cgi?id=593240

[ryandesign (Ryan Carsten Schmidt)]

Duplicate of #21624. Was "fixed" for the moment by downgrading to 1.24.5.