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

Disable chromium metrics providers #26294

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

atuchin-m
Copy link
Collaborator

@atuchin-m atuchin-m commented Oct 29, 2024

For brave/brave-browser#41947

Chromium collects a lot of metrics to send via UMA/UKM.
We don't need them, because we don't send them anyway.
Disabling this helps to save some CPU and memory.

TODO:

  • check crash reporting

Submitter Checklist:

  • I confirm that no security/privacy review is needed and no other type of reviews are needed, or that I have requested them
  • There is a ticket for my issue
  • Used Github auto-closing keywords in the PR description above
  • Wrote a good PR/commit description
  • Squashed any review feedback or "fixup" commits before merge, so that history is a record of what happened in the repo, not your PR
  • Added appropriate labels (QA/Yes or QA/No; release-notes/include or release-notes/exclude; OS/...) to the associated issue
  • Checked the PR locally:
    • npm run test -- brave_browser_tests, npm run test -- brave_unit_tests wiki
    • npm run presubmit wiki, npm run gn_check, npm run tslint
  • Ran git rebase master (if needed)

Reviewer Checklist:

  • A security review is not needed, or a link to one is included in the PR description
  • New files have MPL-2.0 license header
  • Adequate test coverage exists to prevent regressions
  • Major classes, functions and non-trivial code blocks are well-commented
  • Changes in component dependencies are properly reflected in gn
  • Code follows the style guide
  • Test plan is specified in PR before merging

After-merge Checklist:

Test Plan:

@atuchin-m atuchin-m self-assigned this Oct 29, 2024
@atuchin-m atuchin-m marked this pull request as ready for review October 31, 2024 19:57
@atuchin-m atuchin-m requested review from a team as code owners October 31, 2024 19:57
@atuchin-m atuchin-m changed the title WIP: Disable chromium metrics providers Disable chromium metrics providers Oct 31, 2024
@atuchin-m
Copy link
Collaborator Author

A test build to check crash reporting: https://ci.brave.com/job/test-brave-browser-build-macos-arm64/713/

// This object is created by the metrics service before threads, but it
// needs the UserPerformanceTuningManager to exist. At this point it's
// instantiated, but still needs to be initialized.
performance_manager::MetricsProviderDesktop::GetInstance()->Initialize();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can we chromium_src MetricsProviderDesktop to make Initialize() a noop, instead of this patch?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The issue is GetInstance() == nullptr, not with Initialize().

We can try to use chromium_src for this file to replace MetricsProviderDesktop to someFake MetricsProviderDesktop

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants