Extension CPU Hog Hunter

Automatically catch the Chrome extension update that maxes out your CPU

Problem

Browsers freeze and run hot, so users disable extensions one by one; a single V2EX Polish update left a Service Worker in an infinite loop eating a full core, and only a thread of users confirmed it. Nothing tells you which extension started misbehaving after yesterday's update.

Solution

A side panel samples each extension's background CPU and memory, aligns samples with extension update times, and flags ones that started hogging after an update, with one-click disable or rollback. Alerts can be pushed to phone.

Users

Developers and heavy browser users who run many Chrome extensions

MVP

Read extension list and update timestamps; sample per-extension background CPU/memory; auto-flag anomalies on the update timeline; one-click disable; local-only storage

Revenue

One-time purchase or low annual subscription; per-seat IT inspection edition

Why now

Auto-update performance regressions are common yet unmonitored; Chrome extension APIs are enough for an offline build with no backend