Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Bug] Intermittent network connections can create high cpu-use situations for desktop applications.

Open
#1,629 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp

Research direction

No source file or test is named. Start by tracing Firebase Auth initialization after opening the desktop app without internet, then reproduce the repeated “USE_AUTH_EMULATOR not set” output during connection loss. Done means intermittent connectivity no longer causes unbounded log spam or significant CPU load.

Written by the indexing model from the issue text.

Description

api: auth new type: question
[REQUIRED] Please fill in the following fields:
  • Pre-built SDK
  • Firebase C++ SDK version: 11.6.0
  • Problematic Firebase Component: Auth
  • Other Firebase Components in use: Database/Functions/Storage
  • Platform you are using the C++ SDK on: Windows
  • Platform you are targeting: Desktop
[REQUIRED] Please describe the issue here:

Intermittent network connections can create high cpu-use situations for desktop applications.

Steps to reproduce:
  • Sign into firebase auth.
  • Close app.
  • Remove internet.
  • Open app and instantiate a user.

or

  • interrupt internet access.

The following spams the console thousands of times:

INFO: USE_AUTH_EMULATOR not set.
INFO: USE_AUTH_EMULATOR not set.

This creates significant CPU load and overhead when the network connection is lost. I expect the attempt to connect to a live auth instance fails, but there is no rate limit on retries after time 'x', or graceful management of that particular scenario.

Dominant language
C++
Stars
326
Forks
138
Avg merge
2d 16h
Merged PRs (30d)
3

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from firebase/firebase-cpp-sdk

All issues in firebase/firebase-cpp-sdk

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.