Firebase Crashlytics and Performance causes a memory leak at app launch.

[RaccBigenner]

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.

import FirebaseFirestoreSwift
import FirebaseFirestore

func toLoadFireStore(id: String, completion: @escaping (String) -> Void)  {
    
    Firestore.firestore().collection("users").document(id).getDocument { (snaps, error) in

        completion("")
        return

　}

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

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

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]

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

[rizafran]

Thanks for filing, @RaccBigenner. Could you share the complete stack trace of your issue to see what's causing it?

[RaccBigenner]

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

func toLoadFireStore(id: String, completion: @escaping (String) -> Void)  {
    
    Firestore.firestore().collection("users").document(id).getDocument { (snaps, error) in

        completion("success")
        return

        if let error {
            print("Error in toLoadFireStore: \(error.localizedDescription)")
            completion("notAccess")
            return
        }
        
        guard let document = snaps else {
            print("Document does not exist")
            completion("notFind")
            return
        }
        
        guard let data = snaps?.data() as? [String:Any] else {
            completion("isUnmatch")
            return
        }
        
        if let dataSize = try? JSONSerialization.data(withJSONObject: data, options: []).count {
            print("Data size in bytes: \(dataSize)")
        } else {
            print("Failed to calculate data size")
        }
}

Caller processing

toLoadFireStore(id: savedUserID) { result in
                        switch result {
　default: print("ok")
}

[morganchen12]

Can you profile your app via Xcode Instruments and share the trace here?

[RaccBigenner]

Xcode Instruments 経由でアプリをプロファイリングし、ここでトレースを共有できますか?

Untitled.trace.zip

How do you like this?

[morganchen12]

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.

[RaccBigenner]

Please specify how to share a sample project.

[morganchen12]

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.

[RaccBigenner]

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?
I would like you to take a look at the project there.

[RaccBigenner]

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? I would like you to take a look at the project there.

Can you see it?

[morganchen12]

@RaccBigenner sorry for the slow response. You can invite me to your private repository. I haven't received an invitation yet.

[RaccBigenner]

@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.

[morganchen12]

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.

[RaccBigenner]

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 couldn't understand this.
Does this mean that Google Ads is the cause of the memory leak?
When I tried it, the crash occurred even when I skipped ad loading.

I was not able to reproduce a crash in the app.

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.
8825CE71-1E20-4287-9A86-76F907A45EA8

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.

[RaccBigenner]

Please open this issue.

[morganchen12]

I cannot sign your app to build it to a device. Does the crash occur if you disable or remove Firebase?

[RaccBigenner]

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.
This occurs only when communicating with firebase at a large capacity.

Is there any way I can pinpoint the problem?

[morganchen12]

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