I’m looking for some help on reporting a crash bug in Mac OS X and/or Cambria. I don’t know whether it’s the font or the OS (CoreText) or both that are at fault here, and I have no idea where to report this problem other than here.
Here are the steps to repeat the bug:
- Open TextEdit (happens in other apps too).
- ⌘T, change font to Cambria (I have v. 5.97 installed).
- Enter the following characters in order:
- U+00F3 Latin small letter O with acute
- U+0328 Combining ogonek
The crash happens inside of CoreText. It blows up inside of TGlyphComposer::ComposeGlyphs() as can be seen from the top few calls on the stack dump.
0 com.apple.CoreText 0x00007fff830b6c9d TGlyphComposer::ComposeGlyphs(long, TStackBuffer const&) + 1701
1 com.apple.CoreText 0x00007fff830b5e7c TCombiningEngine::ResolveCombiningMarks() + 602
2 com.apple.CoreText 0x00007fff8309e5d7 TTypesetterRunArray::DoAttachments(TLine&) const + 73
3 com.apple.CoreText 0x00007fff8309e4c4 TTypesetterRunArray::TTypesetterRunArray(__CFArray const*, __CFString const*, void const* (*)(__CTRun const*, __CFString const*, void*), void*) + 228
4 com.apple.CoreText 0x00007fff8309e2d9 CTTypesetterCreateWithRunArray + 97
This only seems to happen with Cambria, and not with any other fonts. That’s why I’m not sure whether it’s an OS problem or a font problem. If it’s an OS problem, I have no idea where to report it. I guess can probably look forward to not hearing about it for a year or two, then being forced to upgrade to 10.7 or something. But If it’s a font problem, then maybe someone here can help. In either case, Apple has something to fix since a badly behaved font should still not cause a crash.
The workaround is fairly simple, just using the other possible combination of diacritic and base character: U+01EB Latin small letter O with ogonek + U+0301 Combining acute accent. It’s annoying to have to remember to enter things in one way and not another, and I am wary of other combinations of diacritics giving me problems...