Font Book crashes on macOS 26.0 due to corrupted showDetailPane key in user preferences

After upgrading to macOS 26.0, Font Book consistently crashes on launch for my main user account.


When launching Font Book normally, it attempts to restore saved UI state and crashes with EXC_BREAKPOINT (SIGTRAP) inside +[NSApplication _crashOnException:]. The backtrace points to SwiftUI / AppKit layout code (NSHostingView, ToolbarBridge).


If I launch Font Book with the flag:


open -na "Font Book" --args -ApplePersistenceIgnoreState YES


the app works correctly. This indicates the crash is related to corrupted persisted state.


Observed Results:


  • Font Book crashes immediately with SIGTRAP.
  • User defaults show a suspicious value for showDetailPane:
showDetailPane = {length = 4, bytes = 0x74727565};

This is ASCII “true” stored as raw data instead of a boolean. When Font Book reads this value, state restoration fails and causes a crash.



  • A fresh user account does not show the issue (no corrupted preferences).
  • Deleting ~/Library/Preferences/com.apple.FontBook.plist is not sufficient; the value regenerates as data instead of bool.
  • The only reliable workaround is launching with -ApplePersistenceIgnoreState.
  • Font Book icon also shows incorrectly (Thai “A” glyph instead of the usual “A”), possibly related to corrupted resource or locale fallback.



[Re-Titled by Moderator]

Original Title: Font Book crashes on launch due to corrupted persisted state (showDetailPane key saved as NSData instead of bool)


MacBook Pro 14″, macOS 26.0

Posted on Sep 23, 2025 8:07 AM

Reply
Question marked as Top-ranking reply

Posted on Oct 15, 2025 4:57 AM

Thank you! This terminal command worked for me to open the app as well. Once the app was opened, I closed all detail pains and now I can open the app normally.


I did not have the "Thai Glyph" issue the OP posted, though. YMMV

8 replies

Oct 19, 2025 12:12 PM in response to byanyothername

In case anyone else, besides me, doesn't know how to close "detail panes", I asked claude.ai. I knew what to ask Claude because of byanyothername's post — THANK YOU!


This is the report I got and it worked. I had to use the "View" menu option because I didn't find any hide/show options in the panes except in the font list pane. Font Book opened fine after that and I was able to reopen the detail panes without any issues.


How to Close the Detail Panes

When Font Book is open (launched the safe way from Terminal):

  1. Look for sidebars or panels on the right or bottom of the window showing font details, character previews, or font information
  2. Close these panels using one of these methods:
    • Click the hide/show button (usually in the toolbar or top-right corner of each panel)
  • Use the View menu at the top of the screen - look for options like:
      • "Hide Preview"
      • "Hide Font Info"
      • "Hide Details"
  • Or any checkmarked panel options - uncheck them
  • Try keyboard shortcuts: ⌘+1, ⌘+2, ⌘+3 often toggle different panes
  1. Once you've hidden all the extra panels and are looking at just the basic font list, quit Font Book normally (⌘+Q or Font Book > Quit)
  2. Relaunch normally from your Applications folder or Launchpad

The key is that closing the detail panes and quitting normally will save a "clean" window state. The next time Font Book opens, it should remember this simpler layout instead of trying to restore the problematic configuration that was causing the crash.

Sep 29, 2025 5:17 AM in response to 毛亚琛

Some EtreCheck users have been reporting similar problems. There's something in the window restoration logic of recent updates that leads to crashes. Most of my reports come from people using the most recent versions of Ventura.


Try holding down the shift key when launching the app. That should clear out the window restoration logic. It should launch normally after that, without holding down the shift key every time.


And if it happens again, try the shift key fix again.

Sep 29, 2025 5:03 AM in response to 毛亚琛

I don't have the technical expertise to evaluate the crash report, but Font Book is crashing for me, too, in MacOS 26. Running the Terminal command worked. I submitted a bug report to Apple. I asked Claude.ai to explain the crash report, and this was the response:


What Crashed

  • App: Font Book
  • When: September 29, 2025 at 7:36 AM
  • Your Mac: M4 Pro Mac mini running macOS 26.0

Why It Crashed

The app hit a programming error related to window layout and constraints. Specifically:

  1. The Problem: Font Book's interface (built with SwiftUI) was trying to update how elements are positioned on screen
  2. What Went Wrong: The system detected that views were improperly trying to update their layout constraints in a way that wasn't allowed
  3. The Result: macOS deliberately crashed the app to prevent worse problems (this is called a "breakpoint exception")

The Technical Issue

Looking at the crash trace, the problem occurred when:

  • SwiftUI was updating the toolbar preferences
  • This triggered a cascade of view layout updates
  • Something in the view hierarchy tried to update constraints at the wrong time
  • The system caught this illegal operation and terminated the app

What This Means for You

  • Your computer is fine - this is an app bug, not a system problem
  • Your data should be safe - the crash happened during a UI update, not while working with fonts
  • It's likely a bug in Font Book - particularly around how it handles toolbar and window layout updates

What You Can Do

  1. Restart Font Book - it should work normally most of the time
  2. Report it to Apple - use the crash reporter that likely appeared
  3. Watch for patterns - if it crashes repeatedly doing the same thing, avoid that action until an update fixes it
  4. Keep macOS updated - Apple may fix this in a future update

This type of crash is typically intermittent and shouldn't prevent you from using Font Book for most tasks.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

Font Book crashes on macOS 26.0 due to corrupted showDetailPane key in user preferences

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.