Crash: SIGSEGV in NRMAHarvestController shouldCollectTraces

[BaoLeTimo]

Description

We are experiencing a recurring production crash that occurs inside the New Relic iOS agent.

The crash happens in NRMAHarvestController at shouldCollectTraces and results in a SIGSEGV (segmentation fault).
Based on the stack trace, the crash originates from New Relic internal code and not from our application logic.

This issue impacts production users and occurs intermittently during the New Relic harvest / trace collection cycle.

Steps to Reproduce

At this time, the crash is not consistently reproducible locally.

Observed behavior:

1. App runs normally in production
2. New Relic performs background harvest / trace collection
3. App crashes with SIGSEGV inside NRMAHarvestController

The crash has been observed multiple times in production and is grouped under the same crash fingerprint.

Expected Behavior

New Relic iOS agent should safely handle harvest / trace collection without causing a crash, even in edge cases such as:

• app background / foreground transitions
• app lifecycle changes
• memory pressure

Relevant Logs / Console output

Crash excerpt (symbolicated):

Exception Type:  SIGSEGV

Thread 0 Crashed:
0   NewRelic                      NRMAHarvestController.m:226
    -[NRMAHarvestController shouldCollectTraces]
1   NewRelic                      NRMAHarvestController
2   CoreFoundation                __CFRunLoopRun
3   CoreFoundation                CFRunLoopRunSpecific
4   UIKitCore                     UIApplicationMain

crashreport-12-23-2025_0731+0700.crash.zip

Your Environment

• Platform: iOS
• Devices observed: iPhone 12 Pro Max (possibly others)
• New Relic iOS agent version: 7.5.11

[Newrelic-Boomi]

https://new-relic.atlassian.net/browse/NR-504247

[cdillard-NewRelic]

Thank you for the report. Sorry you are encountering this crashing issue/ I'm initially unable to reproduce this issue. That area of the code hasn't changed in a few years. Is it possible to add a self contained xcode project that reliably reproduces the issue?

[BaoLeTimo]

Sorry @cdillard-NewRelic , we also can't reproduce this issue on our side, but we saw it on New Relic's Mobile Crash

[cdillard-NewRelic]

Thank you can you please attach the mobile crash file here after tapping "Export Crash Details"? Thank you

[BaoLeTimo]

Thank @cdillard-NewRelic, here's the crash detail
crashreport-12-23-2025_0731+0700.crash.zip

[cdillard-NewRelic]

Can you please share the plain text or a non zip file? thank you!

[BaoLeTimo]

crashreport-12-23-2025_0731+0700.txt

[cdillard-NewRelic]

Can you please add the code you are using to initialize the new relic iOS agent in the app delegate? what feature flags are being used?

[BaoLeTimo]

I don't customize any flags, I'm using the default settings

import NewRelic

class AppDelegate: UIResponder, UIApplicationDelegate {

    // ...

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil) -> Bool {
        NewRelic.start(withApplicationToken: "<MY_APP_TOKEN>")
    }
}