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 in BugsnagSystemState.m #886

Closed
sethfri opened this issue Nov 16, 2020 · 3 comments
Closed

Crash in BugsnagSystemState.m #886

sethfri opened this issue Nov 16, 2020 · 3 comments
Labels
bug Confirmed bug released This feature/bug fix has been released

Comments

@sethfri
Copy link

sethfri commented Nov 16, 2020

Describe the bug

We're seeing a crash of unknown origin that seems to be coming from Bugsnag. We have only seen this crash appear 2 times, affecting 2 customers, so it's pretty rare. I also realize the stack trace isn't particularly helpful, so please let me know if you need info from other threads in the report.

Crashlytics reports this as

Crashed: com.apple.root.default-qos
SIGSEGV 0x0000000af24b6e20

Bugsnag reports this as

EXC_BAD_ACCESS_objc_retain
Attempted to dereference garbage pointer 0xaf24b6e20.

Steps to reproduce

Unknown

Environment

  • Bugsnag version: 6.2.3
  • CocoaPods version: 1.9.3
  • Carthage version (if any): n/a
  • iOS/tvOS/macOS version(s): 13.7.0
  • Simulator or physical device: iPhone 6s
  • XCode version: 12.1
  • Swift version (if applicable): 5.1

Stack Trace

Stack trace:
Crashed: com.apple.root.default-qos
0  libobjc.A.dylib                0x18c299980 objc_retain + 16
1  Cash                           0x10184a52c -[BugsnagSystemState sync] + 203 (BugsnagSystemState.m:203)
2  libdispatch.dylib              0x18c2219a8 _dispatch_call_block_and_release + 24
3  libdispatch.dylib              0x18c222524 _dispatch_client_callout + 16
4  libdispatch.dylib              0x18c1cab54 _dispatch_queue_override_invoke + 684
5  libdispatch.dylib              0x18c1d7438 _dispatch_root_queue_drain + 376
6  libdispatch.dylib              0x18c1d7bf8 _dispatch_worker_thread2 + 124
7  libsystem_pthread.dylib        0x18c273b38 _pthread_wqthread + 212
8  libsystem_pthread.dylib        0x18c276740 start_wqthread + 8
@johnkiely1
Copy link
Member

johnkiely1 commented Nov 16, 2020

Hi @sethfri,

Thanks for raising this, we will take a look and get back to you when we know more.

@nickdowell
Copy link
Contributor

Hi @sethfri if you could let us know the version of your app this crash occurred in, it would help us - thanks!

@mattdyoung mattdyoung added the awaiting feedback Awaiting a response from a customer. Will be automatically closed after approximately 2 weeks. label Nov 16, 2020
@bugsnagbot bugsnagbot added the scheduled Work is starting on this feature/bug label Nov 17, 2020
@johnkiely1
Copy link
Member

johnkiely1 commented Nov 18, 2020

Hi @sethfri.

Just to let you know we have identified and fixed the issue causing this. The fix has been released in v6.2.5.

Thanks again for raising this. We appreciate it.

@johnkiely1 johnkiely1 added bug Confirmed bug released This feature/bug fix has been released and removed awaiting feedback Awaiting a response from a customer. Will be automatically closed after approximately 2 weeks. scheduled Work is starting on this feature/bug labels Nov 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Confirmed bug released This feature/bug fix has been released
Projects
None yet
Development

No branches or pull requests

5 participants