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

EXC_BAD_ACCESS from C++ has no thread with current or crashed #1267

Open
philipphofmann opened this issue Aug 9, 2021 · 10 comments
Open

EXC_BAD_ACCESS from C++ has no thread with current or crashed #1267

philipphofmann opened this issue Aug 9, 2021 · 10 comments

Comments

@philipphofmann
Copy link
Member

philipphofmann commented Aug 9, 2021

Environment

Cocoa 6.2.1

Steps to Reproduce

No idea how to reproduce this. Only happens for one customer so far. The app is a game and the problem occurs sometimes when a EXC_BAD_ACCESS happens in .mm code. Event JSON in Notion, as we can't share further details here.

Expected Result

At least one thread should have current or crashed for better grouping.

Actual Result

No thread has current or crashed and this messes up grouping as Sentry groups by exception message.

@bruno-garcia
Copy link
Member

We'd need a repro to look deeper into this.

@kevinneo
Copy link

kevinneo commented Sep 13, 2021

@bruno-garcia
Copy link
Member

@kevinneo the problem in you case is that your Sentry server doesn't have the system symbols. It's visible in the symbols list that they are all red/missing. Same situation as this forum post.

@kevinneo
Copy link

@bruno-garcia EXC_BAD_ACCESS has no thread with current or crashed, this is the question I want to talk about, not missing system symbols.

@philipphofmann
Copy link
Member Author

Thanks, @kevinneo, for pointing out an example. Can you maybe give us more context into the crash itself? What is causing it? What's happening before? We currently have no idea why our SDK has this problem.

@kevinneo
Copy link

kevinneo commented Sep 29, 2021

@philipphofmann Thank you very much for your reply,I got lots of crash issues about that, but in fact I don’t know what caused it and how to reproduce it. As far as I know, there are a few key points:

1、The title message seems to be related to the image loading,such as:

  • "KLWR > Raw profile type exif > Raw profile type iptc > rdf:"
  • "KLWR > Raw profile type exif > Raw profile type iptc > xmpGImg > xmpGImg:"
  • "KLWR > Raw profile type exif > Raw profile type iptc > xmpBJ > xmpBJ:"
  • "jpeg > jpeg: > KLWR > Raw profile type exif > Raw profile type iptc"
  • "adobe:ns:meta/ > KLWR > nsitionContext",&,N,V_transitionContext"
  • "KLWR > tiff > tiff:"

2、In many cases,the running time of the application is very short, only 1~5s before the crash occurs.

@philipphofmann
Copy link
Member Author

Thanks, @kevinneo, for more detail. Which setup does your app have? Do you use some hybrid SDK like Flutter or ReactNative? Is your app a game? Can you give us more context on which libraries you use?

@kevinneo
Copy link

kevinneo commented Oct 9, 2021

Hi @philipphofmann , my app is not a game, it uses ReactNative, and this is a list of third-party SDKs in use.

  • AFNetworking
  • AliyunOSSiOS
  • BVLinearGradient
  • ChinaMapDeviation
  • CocoaAsyncSocket
  • CocoaLumberjack
  • CommonUISDK
  • DoubleConversion
  • FBLPromises
  • FBReactNativeSpec
  • FBSDKCoreKit
  • FBSDKLoginKit
  • FLEX
  • FirebaseABTesting
  • FirebaseCore
  • FirebaseCoreDiagnostics
  • FirebaseCrashlytics
  • FirebaseInstallations
  • FirebaseRemoteConfig
  • GPUImage
  • GRMustache
  • GZIP
  • GoogleDataTransport
  • GoogleUtilities
  • JRSwizzle
  • KVOController
  • Lottie
  • MBProgressHUD
  • MDHTMLLabel
  • MJRefresh
  • Mantle
  • Masonry
  • MessageThrottle
  • MessagingSDK
  • MetalPetal
  • NHNetworkTime
  • NMRangeSlider
  • PromiseKit
  • Protobuf
  • RCTAnimation
  • RCTBlob
  • RCTImage
  • RCTLinking
  • RCTNetwork
  • RCTSettings
  • RCTText
  • RCTTypeSafety
  • RCTVibration
  • RMPhoneFormat
  • RNCAsyncStorage
  • RNCPicker
  • RNFastImage
  • RNSVG
  • RNSharedElement
  • React
  • ReactCommon
  • ReactNativeAudioToolkit
  • SDKConfigurations
  • SDWebImage
  • SDWebImageWebPCoder
  • SSZipArchive
  • SVGAPlayer
  • Sentry
  • Shimmer
  • SnapKit
  • SocketRocket
  • SupportProvidersSDK
  • SupportSDK
  • Swinject
  • YYAsyncLayer
  • YYModel
  • YYText
  • ZendeskCoreSDK
  • ZipArchive
  • cxxreact
  • folly
  • glog
  • jsi
  • jsinspector
  • jsireact
  • libwebp
  • nanopb

@philipphofmann
Copy link
Member Author

Thanks for the input, @kevinneo. We currently have issues to address that affect more users. We will look into this again in the future.

@github-actions
Copy link

github-actions bot commented Nov 8, 2021

This issue has gone three weeks without activity. In another week, I will close it.

But! If you comment or otherwise update it, I will reset the clock, and if you label it Status: Backlog or Status: In Progress, I will leave it alone ... forever!


"A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Backlog
Development

No branches or pull requests

5 participants