ungoogled-software/ungoogled-chromium

Restore Support for --disable-features=UseEcoQoSForBackgroundProcess

Open

#3,260 opened on Mar 31, 2025

View on GitHub
 (1 comment) (3 reactions) (0 assignees)Python (771 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (18,674 stars)
PR merge metrics
 (Avg merge 3d) (8 merged PRs in 30d)

Description

Description

UseEcoQoSForBackgroundProcess removed

Who's implementing?

  • I'm willing to implement this feature myself

The problem

Hi I noticed that the --disable-features=UseEcoQoSForBackgroundProcess flag has been removed in recent updates. This flag was useful for users who wanted to disable EcoQoS for background processes, allowing for more control over performance.

Could you consider bringing it back or providing an alternative way to disable EcoQoS for background processes?

Thanks!

Possible solutions

Restore support for --disable-features=UseEcoQoSForBackgroundProcess.

Provide an alternative flag or setting to disable EcoQoS for background processes.

Add a configuration option in chrome://flags to control EcoQoS behavior.

Alternatives

No response

Additional context

No response

Contributor guide

Research direction
Investigate the Chromium source code to locate where the disable features=UseEcoQoSForBackgroundProcess flag was removed. Check recent commits in the ungoogled chromium repository or upstream Chromium for removal. Consider reverting that commit or adding an alternative flag. Review the current patches and modifications to re implement this flag in the build configuration.
Tech stack
cpp
Domain
performancedesktop
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
None
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70