-
Notifications
You must be signed in to change notification settings - Fork 611
Memory leak in FirebaseInAppMessagingDisplay #6919
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 couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
Hi @ronenfe, thank you for reaching out. I tried reproducing the issue, but I did not encounter a memory leak. I saw your comment here (#5076 (comment)) and check the findings mentioned in this comment #5076 (comment), however, I still did not see the memory leak. I'm using Firebase BOM v33.13.0, can you share the Firebase version you're using? |
Hi, i use the same bom version. Let me try it on a sample project. |
https://github.com/ronenfe/testFirebase, run and see in profiler growth of allocations, remove implementation("com.google.firebase:firebase-inappmessaging-display") |
Hey @ronenfe, thank you for the MCVE. I was able to reproduce the issue the memory leak. I'll raise this to our engineers and see what we can do here. Thanks! |
You are welcome, it took me a while to pinpoint it to this, it may have conflicts with other included libraries because I think it worked when I removed the rest. Also profiler occasionally doesn't show anything in the list or shows incorrect data due to bugs in that too so it takes an effort to get results there. |
[READ] Step 1: Are you in the right place?
Yes
[REQUIRED] Step 2: Describe your environment
___ (Database, Firestore, Storage, Functions, etc)
[REQUIRED] Step 3: Describe the problem
Just implement this library and see allocations grow to infinity.
See similar issue here which was closed years ago:
#482
The text was updated successfully, but these errors were encountered: