StartWithConfig memory leak

[jorgefrazaocosta]

Describe the bug

When Bugsnag is initiated, Leaks tool says it catch a Memory Leak.

Steps to reproduce

1. Implements 6.28.0 SDK
2. Start Bugsnag using BugsnagConfiguration.loadConfig() and set APIKey
3. Launch instruments
4. Observe memory leak

Environment

• Bugsnag version: 6.28.0
• iOS/tvOS/macOS version(s): 17.3.1
• Simulator or physical device: iPhone 13 mini
• Xcode version: 15.2 or 15.3

[clr182]

Hi @jorgefrazaocosta Thanks for reaching out.

Can you please share a copy of your code for the BugSnag configuration with us for further investigation?

[jorgefrazaocosta]

Hi @clr182,

Yes, I can.

let config = BugsnagConfiguration.loadConfig()
config.enabledErrorTypes.appHangs = false
config.apiKey = /* API KEY */

Bugsnag.start(with: config)

[clr182]

Hi @jorgefrazaocosta

I've passed this issue onto our engineering team who believe this does seem to be an issue on our side. We now have a backlog item aimed at investigating this further when priorities allow. Once we have more information to share we will be sure to reach out again with an update.

[n1tesh]

@clr182 any update on this issue ?

[mclack]

Hi @jorgefrazaocosta and @n1tesh

We have some ideas about what this issue may be caused by, but unfortunately we've been unable to reproduce this using the information provided so far.

Would either of you be able to share a stripped down reproduction application with us for further investigation? As this is a public thread, please feel free to share any further details with us directly by contacting support@bugsnag.com.

[clr182]

Hi :wave:

As this thread has not seen any activity for some time I am going to close this issue out. If you would like to continue this investigation please reach out and we can reopen this issue.