-
-
Notifications
You must be signed in to change notification settings - Fork 332
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
Xcode organizer reports crash on writeBinaryImage
#1892
Comments
What is the error message of the crash, @jaroslavas? When does this happen? Do you maybe have a repro for us? |
What exactly do you mean by that? |
It means crash reports downloaded from iTunes Connect. |
Did this start happening in |
We have not used it for some time, but I'm almost sure it was there before |
It seems like we can't handle a signal properly, and we crash in @armcknight, can you look at the stacktrace above, and do you maybe have any clue what could cause a crash when calling into |
@jaroslavas Could you provide a full crash report for some of these examples? There should be a thread that is indicated as the "Crashed thread", and maybe other info like an exception type or backtrace.
My guess is that since our symbols show up in crash reports (which is normal; our crash handler logic is running to collect crash info) Xcode sees us as a common element amongst the reports and is blaming us. In practice, automatically choosing a frame to blame for a crash report is an inexact art. |
writeBinaryImage
writeBinaryImage
@armcknight Can I send them to the email in your profile? |
Yes, you can send them to [email protected]. |
Interesting finding: I went through several of crashes with different stacks, but all them had one thing in common: app was killed by the watchdog with infamous |
As you pointed out the crash is a watchdog termination. The crash reports you sent me contain
So it seems like the app gets killed because it hangs when being in the background.
It seems like the SentrySDK tries to write a crash report for a signal it received and it gets stuck. I'm not sure what is causing this. Worth checking some forks of KSCrash to see if they updated some logic in files similar to SentryCrashReport, SentryCrashDynamicLinker, and SentryCrashC. Thanks for reporting this @jaroslavas. BTW, if you can come up with a repro for us this would be awesome 👏. |
Looking again at the stack trace, the app has already crashed for some reason, as our signal handler is running ( SentryCrash (and KSCrash, in turn) need to avoid the _dyld call by gathering the list of loaded binary images beforehand. This can be done with |
@jaroslavas, can you tell us the percentage of crashes from the Xcode organizer that crashed on writeOnBinaryImage of the total amount of crashes of the Xcode organizers, so we know how bad this is? Does our SDK miss other crashes as well that the Xcode organizer has? If yes, again could you tell us how many, please? |
This could be related to #1864. |
Actually, most of the crashes are from sentry atm :) Here is a screenshot from TestFlight, version on the bottom has sentry enabled, version on the top has it disabled: |
Thanks for the update, @jaroslavas. I would be surprised if this would be the case for most apps. I'm trying to understand what could cause this, although we already know how to fix it. Do you have any other crash reporting tools installed in parallel or another library that hooks into signal handlers? |
Might also fix #1979. |
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 "A weed is but an unloved flower." ― Ella Wheeler Wilcox 🥀 |
So, is there a plan to fix it before bot closes the issue? :) |
Yes, we definitely plan to fix this. We had a minor set back that delayed this, but we're working to have it fixed. |
As the message says we need a backlog label to avoid the stale bot |
Waiting for getsentry/sentry-cocoa#1892 to be fixed
Any updates on this issue? |
No, not yet, @jaroslavas. Sorry, we didn't have the bandwidth yet to get to that issue. |
Hi @philipphofmann do you have any news? thank you |
Nope not yet; sorry, @jacopom. |
Fixed with #2939 |
Hi @brustolin @philipphofmann
And here is the main thread that crashed:
As you can see Is there any way we can help you debug and fix this? |
@jaroslavas, I think that is a different crash that could be related to this issue, but I would prefer if you could open an new issue for that, please. |
getsentry/sentry-cocoa#1892 is not fixed, or the fix was not enough for us to get sentry back working. We still get crash reports where the source of the crash is reported as Sentry itself.
Platform
iOS
Installed
CocoaPods
Version
7.16.0
Steps to Reproduce
Add sentry to app and start reporting issues.
Expected Result
Crashes should be seen in sentry as well as in XCode organizer.
Actual Result
XCode organizer starts showing a lot of different crashes as one, where Sentrys
writeBinaryImage
is shown as the cause for the crash.The text was updated successfully, but these errors were encountered: