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

CPU Performance Debugging using Task Manager (about:performance) #69

Open
amitnovick opened this issue Mar 31, 2020 · 0 comments
Open

Comments

@amitnovick
Copy link

Hey folks, I have an idea for a proposal, hopefully it's not too late to get it reviewed 😅

Problem

A modern web browser has many moving parts:

  • scripts running in a tab (website scripts, content scripts)
  • scripts running in the background (background scripts)
  • scripts running in a devtools panel
  • other things

When one part consumes too much of the CPU, the current best practice AFAIK is to eliminate possible culprits one by one, by terminating them.

This is a tedious and primitive way of solving CPU-performance-related issues.

Solution

Provide a fine-grained view that displays the consumption of each part (a background extension, a tab, or something else) alongside the Memory column in the Task Manager currently accessed through about:performance.

With this kind of view, it would be much easier for users to identify malfunctioning parts and terminate them efficiently.

Similar solutions:

in Chrome:

Task Manager in Chrome

in Windows 10:

Task Manager in Windows

This solution is borne out of frustrations that I had trying to solve an issue of high CPU spikes on my Firefox desktop, and I would love to be able to improve the state of things by contributing via GSOC!

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

No branches or pull requests

1 participant