After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 596674 - Latest pango break "meld @1.2_1".
Latest pango break "meld @1.2_1".
Status: RESOLVED DUPLICATE of bug 593240
Product: pango
Classification: Platform
Component: general
1.26.x
Other Mac OS
: Normal blocker
: ---
Assigned To: pango-maint
pango-maint
Depends on:
Blocks:
 
 
Reported: 2009-09-28 22:50 UTC by cduvivier
Modified: 2009-09-28 23:16 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description cduvivier 2009-09-28 22:50:09 UTC 
At revision 58293, mac ports has upgraded pango from 1.24.5 to 1.26.0.

This upgrade breaks "meld @1.2_1" (Starting meld makes the
 python interpreter endlessly run some pango code.)

I've build and tried the following configurations:
"pango @1.24.5_0+macosx" works.
"pango @1.26.0_0+macosx" has the issue.
"pango-devel @1.25.6_0+macosx" has the issue.

This issue is also tracked by:
 Ticket URL: <http://trac.macports.org/ticket/21678>
Comment 1 Behdad Esfahbod 2009-09-28 22:56:48 UTC 
This is a PPC-only bug so far, I'm guessing it's big-endian specific.  So far I have no clue.  Marking dupe, any debugging help is welcome.

*** This bug has been marked as a duplicate of bug 593240 ***
Comment 2 cduvivier 2009-09-28 23:12:52 UTC 
This is happening on Intel boxes:
- Core2 Duo MacBook Pro.
- Quad Xeon Mac Pro.

There is no crash, seems like an infinite loop, have killed Python interpreter after it uses 10+ minutes of CPU. Sampling it, it is always busy evaluating some pango code.

To reproduce:
- Download macports.
- sudo port selfupdate
- sudo port install meld
Comment 3 Behdad Esfahbod 2009-09-28 23:16:51 UTC 
Please move the conversation to bug 593240.  I don't have access to Mac OS X.

*** This bug has been marked as a duplicate of bug 593240 ***