Skip to content
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

Performance Issues: Continuous "Tries Left" Log Messages Below Zero #8813

Closed
khaaleoo opened this issue Feb 27, 2025 · 2 comments · Fixed by #8814
Closed

Performance Issues: Continuous "Tries Left" Log Messages Below Zero #8813

khaaleoo opened this issue Feb 27, 2025 · 2 comments · Fixed by #8814

Comments

@khaaleoo
Copy link
Contributor

Operating System

browser (macos)

Environment (if applicable)

chrome latest

Firebase SDK Version

11.3.1

Firebase SDK Product(s)

Performance

Project Tooling

Vue 3

Detailed Problem Description

I am encountering a performance issue with the Firebase JavaScript SDK where the console logs show an excessive number of "Tries left" messages that continue to decrement below zero

Here are the relevant log messages captured:
[2025-02-27T07:39:47.293Z] Performance: Tries left: -1 [2025-02-27T07:39:47.293Z] Performance: Tries left: -3 [2025-02-27T07:39:58.102Z] Performance: Tries left: -5 [2025-02-27T07:40:09.997Z] Performance: Tries left: -7 [2025-02-27T07:40:20.997Z] Performance: Tries left: -9 [2025-02-27T07:40:20.099Z] Performance: Tries left: -12 [2025-02-27T07:40:31.102Z] Performance: Tries left: -14 [2025-02-27T07:40:31.133Z] Performance: Tries left: -15 [2025-02-27T07:40:31.134Z] Performance: Tries left: -17 [2025-02-27T07:40:41.095Z] Performance: Tries left: -18 [2025-02-27T07:40:41.182Z] Performance: Tries left: -20 [2025-02-27T07:40:41.108Z] Performance: Tries left: -22 [2025-02-27T07:40:41.141Z] Performance: Tries left: -24 [2025-02-27T07:40:41.141Z] Performance: Tries left: -25

Image

Steps and code to reproduce issue

  1. Initialize Firebase Performance Monitoring in the application.
  2. Trigger an operation that involves performance tracking.
  3. Ensure that an error occurs in the console, potentially related to navigator.sendBeacon or fetch flTransportFullUrl.
  4. Observe the console logs for "Tries left" messages.
@khaaleoo khaaleoo added new A new issue that hasn't be categoirzed as question, bug or feature request question labels Feb 27, 2025
@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.

@khaaleoo
Copy link
Contributor Author

This PR solve the problem: #8814

@jbalidiong jbalidiong added Repro Needed api: performance and removed needs-triage new A new issue that hasn't be categoirzed as question, bug or feature request labels Feb 27, 2025
@DellaBitta DellaBitta self-assigned this Mar 6, 2025
DellaBitta pushed a commit that referenced this issue Mar 6, 2025

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Modify the retry mechanism to stop when remaining tries is less than or equal to zero, improving the robustness of the retry handling.

Fixes #8813
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment