Too many SIGTERM logs #13117
Comments
|
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
|
+1. The ability to disable catching I understand the reasoning around catching |
|
Pro |
|
We had the same problem. the SDK should have an option to ignore SIGTERM (or simply stop collection unless the need is apparent). we have confirmed that sentry-cocoa has added the ability to disable SIGTERM reports. |
|
@tikidunpon Exactly! It's kind of weird Firebase and Sentry both added SIGTERM tracking at once but Sentry had the same issue reported and quickly fixed it by disabling SIGTERM by default. Can confirm that fixed the issue for Sentry for us. At this point, I'd kill Firebase Crashlytics reporting entirely from our app if it wasn't enabled by default and wouldn't break analytics/remote config. |
|
Please add option to disable. |
|
Please add an option to disable. It's affecting our apps too. We have a share extension that is reporting a bunch of SIGTERM and completely random looking crashes. Bringing our overall crash rate down. |
|
Please add option to disable. |
|
This ruined our Crash-rate monitoring. Please add the option to disable as in the other comments above 🙏 |
|
+1 |
|
I would go even further and make reporting SIGTERMs as crashes something you would need to enable |
+1 |
+1 |
|
Thanks for reporting everyone. I'll inform the engineers about this and see what we can do here. |
|
Hello folks, Sorry about the trouble, we reverted the blamed pr and have released a patch version |
|
HI Exception Message: Crashed: com.apple.main-thread Symbol: __CFRunLoopServiceMachPort |
Any reason why is not available for Carthage users? |
|
The fix will be available for Carthage and zip distributions in 10.29.0, due out the week of July 8th. |
and others
Description
After updating to 10.27.0 I am seeing thousands of nearly identical SIGTERM reports showing in Crashlytics. They look the same across all of my apps. However, they appear to have little value as I can't stop them from happening, and they give very little information about what is going on.
As a result, all it does is pollutes the list of crashes, making it harder to find actual issues that I can address. It would be ideal to be able to turn off SIGTERM log collection, or at least be able to permanently hide them all.
Reproducing the issue
No response
Firebase SDK Version
10.27.0
Xcode Version
15.2
Installation Method
CocoaPods
Firebase Product(s)
Analytics, Crashlytics
Targeted Platforms
iOS
Relevant Log Output
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolvedsnippetReplace this line with the contents of your Package.resolved.If using CocoaPods, the project's Podfile.lock
Expand
Podfile.locksnippetReplace this line with the contents of your Podfile.lock!The text was updated successfully, but these errors were encountered: