-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Crashed: com.google.perf.FPREventsQueue (EXC_BAD_ACCESS KERN_INVALID_ADDRESS) #4399
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 found a few problems with this issue:
|
@rahulOYO Do you have any details about the pattern of these crashes? Does this happen only on a particular iOS version, or particular set of devices? Also, any idea on the volume of this crash? At this time my guess is that this crash is related to the Protobuf packaging. Will continue to investigate more to see what could have caused this crash. |
Hi, iOS 12: 92% The volume is quite less as of now, but its under the top crashes. |
@rahulOYO Can you share all the threads that were active during the time of crash? We are guessing a probable race condition in fetching a cached value that is leading to this crash. I'm suspecting this to be a duplicate of the github issue #4400. Depending on the stack trace will decide and mark this as a duplicate of each other. |
Hey @rahulOYO. We need more information to resolve this issue but there hasn't been an update in 7 days. I'm marking the issue as stale and if there are no new updates in the next 3 days I will close it automatically. If you have more information that will help us get to the bottom of this, just add a comment! |
Hi Team, This crash is not occurring now. I will let you know if got reproduced again. Thanks for your support |
[REQUIRED] Step 2: Describe your environment
Here is the snapshot for all firebase related versions:
[REQUIRED] Step 3: Describe the problem
Steps to reproduce:
Although I can't reproduce the crash but I am getting a lot of crashes for my app on Crashlytics and those are in this queue only.
Stack trace of the FPREventQueue thread
The text was updated successfully, but these errors were encountered: