You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can't reproduce a leak in FSTSerializerBeta, either using our tests or a sample application. Looking at the code I can't see an unbalanced retain/release there either. I did find some other leaks related to SCNetworkReachability and a gRPC leak in FillMetadataArray that I'll look at now.
Can you give some more detail about what you might have been doing to trigger this? Things that might be interesting are the shape of your data or the way you access it.
Also could you get a full copy of that stack trace? It's possible that the leak is not local the the serializer. You can get the stack in text form In Instruments by selecting all stack frames, copying, and pasting into a text editor.
Absent more data there's not much I can do about this because I can't find any leak resembling this. Those I did find were fixed in the PR above.
If you are still able to see the leak in FSTSerializerBeta and can provide the additional information requested above we can reopen this and address it.
.### [REQUIRED] Step 2: Describe your environment
[REQUIRED] Step 3: Describe the problem
We found memory leaks from Firestore the Instruments tool while tracing leaks from other SDK.
Steps to reproduce:
What happened? How can we make the problem occur?

This could be a description, log/console output, etc.
The text was updated successfully, but these errors were encountered: