Skip to content

getAuth is adding new events listeners infinitely #8642

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

Closed
mbret opened this issue Nov 15, 2024 · 7 comments
Closed

getAuth is adding new events listeners infinitely #8642

mbret opened this issue Nov 15, 2024 · 7 comments

Comments

@mbret
Copy link

mbret commented Nov 15, 2024

Operating System

mac

Environment (if applicable)

chrome

Firebase SDK Version

11.0.1

Firebase SDK Product(s)

Auth

Project Tooling

vite

Detailed Problem Description

When calling getAuth at top level module (not in a loop) the performance tabs show events being added infiitely by batch of 2 every second.

This looks like some sort of heartbeat that does not clean up correctly.

Steps and code to reproduce issue

import { getAuth } from "firebase/auth"

const auth = getAuth()

@mbret mbret added new A new issue that hasn't be categoirzed as question, bug or feature request question labels Nov 15, 2024
@google-oss-bot
Copy link
Contributor

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

@jbalidiong jbalidiong added api: auth needs-attention and removed needs-triage new A new issue that hasn't be categoirzed as question, bug or feature request labels Nov 15, 2024
@dlarocque
Copy link
Contributor

dlarocque commented Nov 15, 2024

Hi @mbret, thanks for submitting this issue. Could you please share the full event logs, and highlight which are coming from the Firebase JS SDK? I am not able to observe this behaviour from my test app with getAuth().

@mbret
Copy link
Author

mbret commented Nov 15, 2024

I'm not sure how to find this in the performance tab or memory tab. If I make a blank page and record memory footprint we might be able to pinpoint it. I will try tomorrow.

@sam-gc
Copy link
Contributor

sam-gc commented Nov 19, 2024

This is likely related to #6082 and not a concern.

@mbret
Copy link
Author

mbret commented Nov 19, 2024

Since we can manually trigger the GC I will try to do a repro and do it to see if it effectively get GC or not. Thanks for the linked issue, it seems like it is likely related indeed.

@google-oss-bot
Copy link
Contributor

Hey @mbret. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

@google-oss-bot
Copy link
Contributor

Since there haven't been any recent updates here, I am going to close this issue.

@mbret if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.

@firebase firebase locked and limited conversation to collaborators Jan 3, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants