[go: up one dir, main page]

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

FirebasePerformance crash: EXC_BAD_ACCESS (crashed) KERN_INVALID_ADDRESS #12969

Open
pavel-zaletski opened this issue May 15, 2024 · 2 comments
Assignees

Comments

@pavel-zaletski
Copy link

Description

Crash message:
EXC_BAD_ACCESS (crashed)
KERN_INVALID_ADDRESS
Attempted to dereference garbage pointer 0x8.

From time to time we observe crashes in our app. Unfortunately we can't reproduce it locally. We see them only in Embrace tool

image
image

The issue is similar to the following:
#11403
#12457

Recently we updated Firebase SDK to 10.24.0. But it did not help.

Reproducing the issue

Can't reproduce it locally. Crashes were observed in Embrace tool

Firebase SDK Version

10.24.0

Xcode Version

15.3

Installation Method

CocoaPods

Firebase Product(s)

Analytics, Messaging, Performance

Targeted Platforms

iOS

Relevant Log Output

No response

If using Swift Package Manager, the project's Package.resolved

Expand Package.resolved snippet
Replace this line with the contents of your Package.resolved.

If using CocoaPods, the project's Podfile.lock

Expand Podfile.lock snippet
Replace this line with the contents of your Podfile.lock!
@google-oss-bot
Copy link

I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.

@pavel-zaletski pavel-zaletski changed the title EXC_BAD_ACCESS (crashed) KERN_INVALID_ADDRESS FirebasePerformance crash: EXC_BAD_ACCESS (crashed) KERN_INVALID_ADDRESS May 15, 2024
@pavel-zaletski
Copy link
Author

Hello! Do you have any updates on this?

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

No branches or pull requests

4 participants