-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Firebase Crashlytics and Performance causes a memory leak at app launch. #11725
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 filing, @RaccBigenner. Could you share the complete stack trace of your issue to see what's causing it? |
I don't know what "the complete stack trace of your issue" is, but I will also provide the following information. error handling
Caller processing
|
Can you profile your app via Xcode Instruments and share the trace here? |
How do you like this? |
There's two memory leaks here, one in GoogleMobileAds and one in FirebaseSessions. Unfortunately, the stack trace in Instruments is unsymbolicated. Can you share a sample project that demonstrates this leak? For GoogleMobileAds, you can ask for help in this mailing list. |
Please specify how to share a sample project. |
You can push a project to an empty GitHub repository and then post the link here, or try reproducing this bug in one of our quickstarts. |
Can I invite you to my private repository? |
Can you see it? |
@RaccBigenner sorry for the slow response. You can invite me to your private repository. I haven't received an invitation yet. |
I invited you. See LogNestOfStory.xcodeproj. |
The sessions leak is a regression of #11027. You can request help for the Google Ads memory leak here: https://support.google.com/admob/topic/12676598 I was not able to reproduce a crash in the app. |
I couldn't understand this.
Here are the steps to reproduce the app crash. First, start it on the actual machine. Next, enter the following into the transfer code input field as "引き継ぎID入力" on the title screen. In that state, tap the title screen to start the game. From there a memory leak occurs and the app crashes. By the way, I don't know why you can't reproduce it in the simulator. It may be related to the cause of this problem. |
Please open this issue. |
I cannot sign your app to build it to a device. Does the crash occur if you disable or remove Firebase? |
No, it doesn't happen. Is there any way I can pinpoint the problem? |
You can use the Allocations tool in Xcode Instruments to determine what is allocating the memory that causes the crash: https://developer.apple.com/documentation/xcode/gathering-information-about-memory-use |
Description
When I go to Firesotre, the CPU and memory increase and the app crashes.
It doesn't matter how much data you have, it can happen with more or less data.
If you do it on the real machine, it will crash as above, but if you do it on the simulator, the CPU and memory will increase, but it will not crash.
The following is repeatedly output on the simulator.
2023-08-20 22:09:22.810732+0900 xxx[10198:8177038] [connection] nw_connection_copy_protocol_metadata_internal_block_invoke [C580] Client called nw_connection_copy_protocol_metadata_internal on unconnected nw_connection
2023-08-20 22:09:14.007917+0900 xxx[10198:8177038] [connection] nw_connection_copy_connected_local_endpoint_block_invoke [C562] Client called nw_connection_copy_connected_local_endpoint on unconnected nw_connection
2023-08-20 22:10:02.785020+0900 xxx[10198:8177023] [connection] nw_connection_copy_connected_remote_endpoint_block_invoke [C659] Client called nw_connection_copy_connected_remote_endpoint on unconnected nw_connection
xxx is the application name.
Reproducing the issue
The relevant code is below.
I'm sure it's not elsewhere.
Firebase SDK Version
10.14.0
Xcode Version
14.3.1
Installation Method
Swift Package Manager
Firebase Product(s)
Database, Firestore
Targeted Platforms
iOS
Relevant Log Output
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
snippetReplace this line with the contents of your Podfile.lock!
The text was updated successfully, but these errors were encountered: