fontd is stuck in ScanForChangesInDirectory

Originator:SaagarJha28
Number:rdar://33141043 Date Originated:5-Jul-2017 01:06 PM
Status:Duplicate/32475666 Resolved:
Product:macOS + SDK Product Version:macOS High Sierra 10.13 Beta (17A291m)
Classification:Crash/Hang/Data Loss Reproducible:
 
Area:
Something not on this list

Summary:
fontd seems to stuck at 100% CPU since startup, apparently in due to an infinite loop in ScanForChangesInDirectory (see attached sample). Killing it does not resolve the issue. A sysdiagnose is attached.

Steps to Reproduce:
Not sure–it was just this way after restarting.

Expected Results:
fontd isn't stuck.

Observed Results:
fontd is stuck.

Version:
macOS High Sierra 10.13 Beta (17A291m)

Notes:


Configuration:
Early 2015 MacBook Pro with Retina Display running macOS High Sierra 10.13 Beta (17A291m)

Comments


Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!