Repository navigation
Glyphs render enlarged/bold after heavy redraw (spinner + progress bar); only killing the process restores them #14944
Unanswered
mangxy
asked this question in
Issue Triage
Replies: 1 comment
|
There's a good chance that this is related to font fallback not being deterministic. You can actually specify multiple font families to control the fallback. Set
|
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Environment
Setup
The configured font lacks glyphs for U+25D0, U+25B0, U+25B1 — verified across all 16 weights of the family via fontTools cmap (only U+25D4 and U+25CF exist). These characters therefore always render through the coretext fallback path.
Trigger
Running Claude Code (CLI TUI). Its Bash tool shows a spinner built from those moon-phase circle glyphs that redraws every frame, and its /compact command renders a progress bar of shaded/unshaded block glyphs with continuous redraws.
Symptom
After a session with sustained spinner/progress redraws:
Recovery
This suggests the corrupted state lives in a process-level cache (glyph atlas / font fallback resolution) shared across windows, and it never self-heals once corrupted.
Attempted workarounds (no effect)
grapheme-width-method = unicode(already the default)font-codepoint-mappinning — retracted, since the pinned font has no glyphs for these codepointsRepro
Use a terminal font missing the moon-phase (U+25D0 range) and block-element (U+25B0 range) glyphs, run a TUI that redraws these characters at high frequency for a while, then compare glyph size before/after.
All reactions