Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Crash] EXC_BAD_ACCESS in bsg_kscrashstate_i_onIntegerElementon Bugsnag startup, attempting to load persistent state of crash context #218

Closed
jessesquires opened this issue Dec 4, 2017 · 4 comments
Labels
bug Confirmed bug

Comments

@jessesquires
Copy link

jessesquires commented Dec 4, 2017

Expected behavior

Calling -[Bugsnag startBugsnagWithApiKey:] doesn't crash.

Observed behavior

Calling -[Bugsnag startBugsnagWithApiKey:] crashes.

Steps to reproduce

Unsure, but this is happening on application launch. We call -[Bugsnag startBugsnagWithApiKey:] in the AppDelegate.

The crash is happening here, in bsg_kscrashstate_i_onIntegerElement in the call to strcmp. name is NULL, which seems to be the issue.

Version

5.13.3, 5.14.1 (possible that earlier version are affected)

Stack trace

screen shot 2017-12-04 at 11 25 47 am

@kattrali
Copy link
Contributor

kattrali commented Dec 4, 2017

Thanks, @jessesquires. Looking into it.

@kattrali
Copy link
Contributor

kattrali commented Dec 4, 2017

Which version were you using before 5.14.1?

@jessesquires
Copy link
Author

@kattrali We were on 5.13.3, which also experiences the issue. (Will update original comment)

@kattrali kattrali added the bug Confirmed bug label Dec 4, 2017
@kattrali
Copy link
Contributor

kattrali commented Dec 6, 2017

@jessesquires Can you send me a crash report from a device via [email protected] ? I've found some potential leads but haven't reproduced this case. In general, reading/writing to disk seems to be working correctly when using 5.14.1 (and with stored reports generated on 5.13 and earlier).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bug
Projects
None yet
Development

No branches or pull requests

2 participants