Log in

Tue, May. 13th, 2008, 12:09 pm
Process list for my new OS

The web browser is the new operating system. My own computer is at this point little more than a glorified web browser, with a text editor, command prompt, python interpreter and svn thrown in for the occasional color.

Since the web browser is the new OS, it should really, really, have the equivalent of a process list. I almost always have a whole bunch of tabs open, and firefox is most of the time using a nontrivial amount of CPU doing not much of anything. I have to guess which tab is causing the problem when the CPU gets pegged, and sometimes it seems that even shutting down all tabs doesn't completely fix the problem. Could somebody please implement metrics on how much CPU each tab/window is using, and get the process separation right so that whenever a tab/window is shut down all remnants of it are completely toast?

Wed, May. 14th, 2008 05:57 pm (UTC)
jeffdaly: Mozilla is working on it - see Firefox extension PluginWatcher

There actually is some work being done in Mozilla to address this sort of thing. Firefox 3, which is currently still in development (but nearly done) includes XPCOM hooks for monitoring plugin performance with nsIObserverService. See bug 412770 for details on how it came about. Fima Kachinski has authored an addon, Plugin Watcher that implements the service and displays a load meter in the status bar. It could use a lot more work, but at least it's a start.

Personally, I'd like to see something in the style of Firebug's Network Monitoring Traces. But should observe all the tabs loaded in the browser, and break down the activity to show which addon, plugin or native piece of code is hogging the CPU.

Thu, Aug. 14th, 2008 04:56 pm (UTC)
zaitcev: Re: Mozilla is working on it - see Firefox extension PluginWatcher

Plugins are only a small part of the problem. More commonly there's an issue with JavaScript or other inside one of the tabs and you have to close half of them before lucking upon the one that hogs the CPU. IMHO, per-tab separation is more important than per-plugin separation.