0 CoreText TDecorationRun::CalculateGlyphIntersections(CGAffineTransform, TRun const&, double, double, std::__1::function<void (double, double)> const&) const + 1704 1 CoreText TDecorationRun::CalculateGlyphIntersections(CGAffineTransform, TRun const&, double, double, std::__1::function<void (double, double)> const&) const + 1440 2 CoreText void TDecorationRun::DrawDecorationRun<(anonymous namespace)::TRunAdapter>(CGContext*, (anonymous namespace)::TRunAdapter, (anonymous namespace)::TRunAdapter, double)::'lambda'(CGPoint, CGPoint)::operator()(CGPoint, CGPoint) const + 508 3 CoreText TDecorator::DrawDecoration(TLineDrawContext const&, TLine const&, TInlineVector<DecorationOverride, 30ul> const*) + 2356 4 CoreText TLine::DrawUnderlines(CGContext*) const + 104 5 CoreText TLine::DrawGlyphs(CGContext*) const + 292
iOS18，CoreText EXC_BREAKPOINT
Can you provide more information about, say, the code that is running when you see this exception?
I'm also having this issue, coming from production app, we are not able to reproduce. The only thing we know is that it's from CoreText and here TDecorationRun::CalculateGlyphIntersections.
It's very specific to some users, about 50, but we already have 500 crash events for those 50 unique users.
Can you provide a complete crash log? Or a listing of the code that you suspect is running at the time of the crash?
Hello,
We don't have specific points of the app code where it may be crashing, since it's random, we already seen code crashing at very different locations around the app. Currently, about 5% of our users base is having this crash, also another detail, we are seeing this around different versions of iOS, not specific to iOS 18 or 26. We suspected at first about the compiler of new Xcode 26 (since this was the first version compiled with new Xcode), but it seems it is not that. We have sent a new build out today, compiled with Xcode 16.4, but no luck, still crashes.
I'm attaching 2 screenshots, from the crashing stacktrace, one from Sentry and the other one from Xcode crash reporter directly. Also, attached the .crash file with the full stacktrace that can be found at Xcode.
Thanks for the crash log. This doesn't appear to be Core Text related. It looks more like it's related to a CATransaction being processed in the main loop. In these cases I usually suggest looking for some other thread that is trying to do something that may simultaneously access something that Core Animation is using - even something as simple as accessing a property since that can potentially run code.