[MacPorts] #52099: fontconfig performance problem from r149841 to r151014

[MacPorts]

#52099: fontconfig performance problem from r149841 to r151014
-------------------------+--------------------------
  Reporter:  ken@…       |      Owner:  ryandesign@…
      Type:  defect      |     Status:  new
  Priority:  Normal      |  Milestone:
 Component:  ports       |    Version:  2.3.4
Resolution:              |   Keywords:
      Port:  fontconfig  |
-------------------------+--------------------------
Description changed by mf2k@…:

Old description:

> When I run the "emacs +x11" port or the "tkdiff" port (with "tk +x11")
> with the latest "fontconfig" port, I see a long delay before the program
> pops up the window.  In ActivityMonitor, I see the program using ~100% of
> a core.  If I sample the process, I see it's spending almost all of its
> time in libfontconfig.1.dylib.
>
> So, I reverted my fontconfig port from r151014 to r149841 (from the
> latest to the second latest).  The problem goes away -- emacs or Tcl/Tk
> programs start right away.
>
> I've gone back and forth multiple between the two versions multiple times
> and the problem reproduces itself.  I've seen this on two different Macs
> running El Cap.  All my other MacPorts stuff is up-to-date and I'm
> running the latest XQuartz.
>
> The may very well be the same root cause as
> https://trac.macports.org/ticket/52088.
>
> Thanks!

New description:

 When I run the "emacs +x11" port or the "tkdiff" port (with "tk +x11")
 with the latest "fontconfig" port, I see a long delay before the program
 pops up the window.  In ActivityMonitor, I see the program using ~100% of
 a core.  If I sample the process, I see it's spending almost all of its
 time in libfontconfig.1.dylib.

 So, I reverted my fontconfig port from r151014 to r149841 (from the latest
 to the second latest).  The problem goes away -- emacs or Tcl/Tk programs
 start right away.

 I've gone back and forth multiple between the two versions multiple times
 and the problem reproduces itself.  I've seen this on two different Macs
 running El Cap.  All my other MacPorts stuff is up-to-date and I'm running
 the latest XQuartz.

 The may very well be the same root cause as #52088.

 Thanks!

--

-- 
Ticket URL: <https://trac.macports.org/ticket/52099#comment:3>
MacPorts <https://www.macports.org/>
Ports system for OS X