amitnovick/catalog 16

Catalog - a file manager application for Desktop

amitnovick/8dc5 0

Browser's Castle

amitnovick/catalog-docs 0

Documentation site for Catalog

amitnovick/clean-code-javascript 0

:bathtub: Clean Code concepts adapted for JavaScript

amitnovick/clj-usage-graph 0

Haxy usage graphs for Clojure projects

amitnovick/create-react-app 0

Set up a modern web app by running one command.

amitnovick/emotion 0

👩‍🎤 CSS-in-JS library designed for high performance style composition

issue openedmozilla/GSOC2020

CPU Performance Debugging using Task Manager (about:performance)

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


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.


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!

created time in 2 months