-
Notifications
You must be signed in to change notification settings - Fork 1.6k
GRCP Sigsev crash since iOS18+firestore #14117
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
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Thanks for reporting @miklosmagyar . This is probably a duplicate of #14018, which we've sadly not been able to reproduce and debug. Are you able to reproduce this locally using the emulator? If so, would you be able to share a reproduction code with me (e.g. using a github repository). Meanwhile I'll use your stacktraces to dig further into the code to see if I can spot anything suspicious. |
I've been putting all of my findings over on #14018 . I believe I've tracked down quite a bit - just not sure why there would be a limit on how many stream objects can be loaded. Hopefully that helps point you guys in the right direction. |
@ehsannas So it seems like this issue mostly happens when the internet connection is pretty bad or it goes off. Maybe this is aligned with that usecase as well when the app goes and stayes in the background. Here is the log what I received:
I hope this helps guys |
Thanks for the update @miklosmagyar . I looked through the code around the ASAN stack and it's sadly not useful. It also appears that this ASAN stack is not relevant to the crash you're observing in Crashlytics. |
I'll spend some more time to see if I can reproduce the error by having a stream with a large result set and then putting it in the background. |
Description
Our team experiencing a lot of crashes since iOS18 came into the picture and made the required updates for firebase ecosystem. Seems like all of them are coming from GRCP part. We received this crashes in crashlytics:
After I turned on Address sanitizer + detect use of stack after return I was able to catch this crash in simulator (If I am correct it is the same crash what we are receiving in crashlytics). Below I am attaching the captured crash from XCode:
Reproducing the issue
No response
Firebase SDK Version
11.3
Xcode Version
16.0
Installation Method
CocoaPods
Firebase Product(s)
Analytics, Authentication, DynamicLinks, Firestore, Remote Config, Storage
Targeted Platforms
iOS, watchOS, App Extensions
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
Expand
Package.resolved
snippetReplace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand
Podfile.lock
snippetThe text was updated successfully, but these errors were encountered: