Configuration options for smallest footprint?

[steviec]

I'm attempting to run Sentry within an iOS extensions that has extreme memory footprint limits (6MB). When including Sentry, it increases my footprint by over 1MB, which is too much for my use case. I only use Sentry to detect crashes right now, and I'd like to know if there are other configuration options I can set that lead to the smallest possible memory footprint.

Here's my current config:

    SentrySDK.start { options in
        options.dsn = dsn
        options.debug = false
        options.environment = isDevelopmentMode ? "development" : "production"
        options.enableSwizzling = false
        options.maxBreadcrumbs = 5
        options.maxCacheItems = 1
        options.enableTracing = false
        options.enableCaptureFailedRequests = false
    }

Do you happen to know the small possible footprint that Sentry could consume?

Thanks!

[philipphofmann]

You could add using only the Crash and Breadcrumb integration with this

options.integrations = Sentry.Options.defaultIntegrations().filter { name in
    name == "SentryCrashIntegration" || name == "SentryAutoBreadcrumbTrackingIntegration"
}

That's the smallest you can go right now. If this is still not enough, we could improve the overall footprint of the SDK, which is a major initiative and would take some time.

[steviec]

Correct. I can't run Sentry in our iOS extension because it consumes around 1MB of the extension's memory footprint, even after stopping the binary image cache in ObjC. This pushes our extension's footprint over the 6MB limit, so the kernel kills the process.

I stripped down the extension to a completely minimal version (it only logs to console), and here's what I'm seeing:

• minimal version: ~2000K
• with Sentry added to the podspec (but without calling SentrySDK.start): ~2300K
• with Sentry added to the podspec and calling SentrySDK.start: ~2900K

Thanks for your patience in trying to diagnose this @philipphofmann !

[philprime]

Hi @steviec, just to better understand the use case, what kind of extension are you working on (i.e. App Extension, Safari Extension, Widget Extension, etc.)

[steviec]

It's a DeviceActivityMonitor extension (https://developer.apple.com/documentation/deviceactivity/deviceactivitymonitor) that's part of the DeviceActivity framework (https://developer.apple.com/documentation/deviceactivity).

[philipphofmann]

Thanks for the context again @steviec. I opened a GH issue #4756 but can't give you an ETA yet.

[steviec]

Great, thank you!