Bug 98403

Summary:	Xquartz 2.7.10 Local Launch Of xclock Now Very Slow
Product:	XQuartz	Reporter:	Dick Riegner <dickie>
Component:	New Bugs	Assignee:	Jeremy Huddleston Sequoia <jeremyhu>
Status:	RESOLVED DUPLICATE	QA Contact:	Jeremy Huddleston Sequoia <jeremyhu>
Severity:	normal
Priority:	medium
Version:	unspecified
Hardware:	Other
OS:	Mac OS X (All)
Whiteboard:
i915 platform:		i915 features:

Description Dick Riegner 2016-10-23 22:29:48 UTC

After upgrading from Xquartz 2.7.9 to 2.7.10 of Mac OS X El Capitan, local launching of xclock is now very slow.  On 2.7.9 it took a second or two, on 2.7.10 it now takes about 20 seconds or longer.  A second launch is just as slow.

Launching other X11 apps such as xeyes does not seem to be impacted;  it still launches in about 2 seconds on 2.7.10.

Launching xclock from a remote Linux client still only takes about 4 seconds on 2.7.10.

While launching xclock is not critical to me, it does look like there may be a new issue in Xquartz 2.7.10 on El Capitan.

Thanks for the help.

Comment 1 Jeremy Huddleston Sequoia 2016-10-24 00:23:38 UTC

                          995  XftInit + 52 (libXft.2.dylib + 69316) [0x1073b8ec4]
                            995  FcConfigInit + 9 (libfontconfig.1.dylib + 17105) [0x10750c2d1]
                              995  FcConfigEnsure + 36 (libfontconfig.1.dylib + 17152) [0x10750c300]
                                995  FcInitLoadOwnConfigAndFonts + 29 (libfontconfig.1.dylib + 66499) [0x1075183c3]
                                  995  FcConfigBuildFonts + 85 (libfontconfig.1.dylib + 18993) [0x10750ca31]
                                    995  FcConfigAddDirList + 126 (libfontconfig.1.dylib + 19212) [0x10750cb0c]
                                      995  FcDirCacheScan + 232 (libfontconfig.1.dylib + 46502) [0x1075135a6]
                                        995  FcDirScanConfig + 445 (libfontconfig.1.dylib + 46063) [0x1075133ef]
                                          990  FcFileScanConfig + 387 (libfontconfig.1.dylib + 45080) [0x107513018]
                                            989  FcFreeTypeQueryFace + 6541 (libfontconfig.1.dylib + 60135) [0x107516ae7]
                                              981  FcFreeTypeCharSetAndSpacingForSize + 327 (libfontconfig.1.dylib + 62597) [0x107517485]
                                                981  FcFreeTypeCheckGlyph + 60 (libfontconfig.1.dylib + 64240) [0x107517af0]
                                                  972  FT_Load_Glyph + 662 (libfreetype.6.dylib + 12201) [0x10754cfa9]
                                                    860  cff_glyph_load + 1446 (libfreetype.6.dylib + 153142) [0x10756f636]
                                                      852  cf2_decoder_parse_charstrings + 2756 (libfreetype.6.dylib + 161239) [0x1075715d7]
                                                        211  cf2_interpT2CharString + 1738 (libfreetype.6.dylib + 164523) [0x1075722ab]
                                                          168  cf2_glyphpath_lineTo + 250 (libfreetype.6.dylib + 173309) [0x1075744fd]

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

Comment 2 Jeremy Huddleston Sequoia 2016-10-24 16:17:29 UTC


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

Comment 3 Dick Riegner 2016-10-25 16:09:11 UTC

I just updated to Xquartz 2.7.11_rc1 and xclock still takes about 20 seconds to launch.  A second launch is still slow.

Comment 4 Jeremy Huddleston Sequoia 2016-10-26 04:54:42 UTC

Then comment in the fontconfig bug.  The change addresses the issue for me...

Comment 5 Jeremy Huddleston Sequoia 2016-10-26 08:15:25 UTC

Actually, the fix didn't get into 2.7.11_rc1 like I thought.  I'll be getting out a 2.7.11_rc2 with it soon.  Sorry for the confusion.

Comment 6 Dick Riegner 2016-10-26 13:56:31 UTC

Thanks for the update. 

So all future comments should be posted to 98338 and not to this bug?

Comment 7 Jeremy Huddleston Sequoia 2016-10-26 16:22:30 UTC

Yes.  Please try 2.7.11_rc2.  If the issue persists, add comments in #97546

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.